CloudShark 2.3.0

Release History

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.2330 September 30th, 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

New Features and Highlights

Single Sign-On

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.

API Tokens for Everyone

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.

Learn more…

Updated Protocol Support

CloudShark 2.3 includes Wireshark 1.12.1 which improves performance, updates several protocols, and adds new dissectors.

Read the official Wireshark release notes

Upgrade Instructions

Read our upgrade instructions for information on obtaining the latest version of CloudShark.

Bug fixes and other changes

  • Disable API tokens belonging to users who get deleted.
  • Moved configuration of external authentication from the main settings page to its own page.
  • Adds links to our Best Practices and the HTTPS Configuration documents from within the settings page.
  • Resolved an encoding issue when importing a file via URL.
  • Upgraded to Ruby 2.1.3 for much lower memory usage.
  • Persist database credentials across future updates. Learn more
  • Improved handling of errors while starting up.
  • Added the total number of users to the Admin dashboard.

Maintenance release 1: CloudShark 2.3.2458 November 13th, 2014

Improved Hex and ASCII Highlighting

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.

Updated to tshark 1.12.2

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:

Bug fixes and other changes

  • Resolved issue preventing the user from turning on external DNS name resolution in their .wireshark preferences file.
  • Fixed missing decoder for the OGG format
  • Added a link to documentation when encountering a bad display filter
  • Resolved a problem displaying VoIP Call Flows for certain kinds of VoIP traffic
  • Display the full name of the User in more places rather than just the login id.
  • Better handling of custom-tshark versions during startup after an update.

Maintenance release 2: CloudShark 2.3.2530 December 2nd, 2014

It’s winter here in New England, so to keep warm we’ve been fixing bugs and adding features to the API. Enjoy!

Add annotations via the API

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.

Example using Curl

curl -X POST https://cloudshark/api/v1/[token]/annotations/42b902afcdee \
     --data "frame=7" \
     --data "text=new annotation added by the api"

Read more about this new API call…

Bug fixes and other changes

  • Fixed an issue preventing capture files from being uploaded when the system LANG is set to a locale that uses commas instead of decimal points.
  • Resolved a bug when scrolling through packets while a display filter was applied that could sometimes result in an error message.
  • Cleaned up a few places where JavaScript could be entered by the Admin user and be executed when visiting subsequent pages.