|Release Type||Release Number||Release Date|
|Original||CloudShark 2.3.2343||September 30th, 2014|
|Maintenance Release 1||CloudShark 2.3.2458||November 13th, 2014|
|Maintenance Release 2||CloudShark 2.3.2530||December 2nd, 2014|
CloudShark 2.3 is here!
In this release, we have added a few new features to our Enterprise tier to better support installations with lots of users. Managing API tokens has been made easier, and there is new authentication possible via Single Sign-On.
We really hope you enjoy using it!
— The CloudShark Team
CloudShark 2.3 brings new authentication options for Enterprise customers. SAML 2.0 support has been added to allow users to sign in through an external Identity Provider bringing their credentials from anywhere in the network.
Read our Support page to learn more about configuring SSO.
New for CloudShark 2.3 is the ability for users to create API tokens for themselves. If you have a lot of users, managing their API access can be difficult. By allowing users to create their own API tokens, it can get them up and running integrated scripts faster and easier than before. This option is off by default and should be enabled by an Admin user.
CloudShark 2.3 includes Wireshark 1.12.1 which improves performance, updates several protocols, and adds new dissectors.
Read our upgrade instructions for information on obtaining the latest version of CloudShark.
This maintenance release improves the HEX and ASCII pane of the decode window within CloudShark. It makes it much easier to select and copy hexadecimal packet data, or ASCII data for use in other analysis.
Just in time, the Wireshark team has released 1.12.2 which includes bug fixes, updates to protocols and specifically a fix for LLDP TIA Policy decoding. You can read the full release notes over on the Wireshark site: https://www.wireshark.org/docs/relnotes/wireshark-1.12.2.html
It’s winter here in New England, so to keep warm we’ve been fixing bugs and adding features to the API. Enjoy!
This maintenance release brings a new API method for adding an annotation to a specific packet on a capture file in CloudShark. It uses the same endpoint for retrieving annotations, but replaces the GET verb with a POST.
curl -X POST https://cloudshark/api/v1/[token]/annotations/42b902afcdee \ --data "frame=7" \ --data "text=new annotation added by the api"
LANGis set to a locale that uses commas instead of decimal points.