||CloudShark 1.5 build 988
||June 19, 2012
||CloudShark Tools 1.32
||CloudShark 1.5 build 1005
||August 6, 2012
Original release: CloudShark 1.5 build 988 June 19, 2012
New Features and Highlights
- New HTTP Requests analysis tool
The new HTTP Requests analysis tool allows users to display a list of hosts and URIs that are being requested the within a capture file. Individual requests can be examined to calculate timing information and inspection of the raw TCP stream.
- New blocked types feature for file uploads
Administrators can now prevent certain file types from being imported into CloudShark, regardless of if they are considered “valid” files or not. For example, MPEG and JPEG files are perfectly readable by CloudShark, however some admins might not want those kinds of files being hosted on their appliance. Blocked file types can be configured in the Administration Menu.
Users can now export saved CloudShark Graphs as PDF documents or PNG or SVG images for inclusion in other report generating tools. The graph export feature is available when viewing saved graphs by pressing the Export as PNG/PDF/SVG button in the toolbar.
- New custom columns in decode view
Users can now customize which columns they see in CloudShark’s decode window. These settings can be stored with the file, so that all users see a chosen set of columns, or can be saved per user so that all files opened by that user include the specified columns. See the User Guide for more information.
Users can now hover over a field in the middle pane of the decode for a capture file to show a mouse tooltip with the name of that field for use in display filters or graphs.
- Improved upload interface
Improved Upload interface now works correctly on Google Chrome, Safari 5+, and the latest Firefox. Other browsers (and older versions of those browsers) are not supported. This resolves the known issue with Google Chrome reported in CloudShark 1.4.
- Upload via URL now supports FTP style URIs
CloudShark’s upload widget now supports FTP style URIs.
- API now supports upload via HTTP PUT method
CloudShark’s API now supports the HTTP PUT method (in addition to the POST method) for API uploads.
- CloudShark plugin for Wireshark has been updated
The CloudShark plugin for Wireshark has been updated to version 1.0.1-162. See this post and the changelog for more information.
Bug Fixes and Notes
- Fixes a problem where the VM time might skew away from the browser time resulting in the inability to log in to cloudshark. A warning is displayed on the login screen if the server’s clock is too far away from the browser’s.
- The capture filename can be specified when using the PUT upload method (Cisco IOS integration).
- Capture files are processed faster the first time they are opened for viewing.
- CloudShark can now display more than one notification banner at the top of the page.
- Display filters using double-quotes work correctly when opening a graph from that display filter.
- CloudShark’s Highstock library has been upgraded to version 1.1.6.
Maintenance release 1: CloudShark 1.5 build 1005 August 6, 2012
New Features and Enhancements
- Support for longer login names User names and passwords are now limited to 50 characters each. In previous releases user names and passwords were limited to 25 characters.
- Upload API method now supports comments Comments can now be provided at upload time using the API upload method’s optional comments parameter.
Bug Fixes and Notes
- Removes confusing external groups language from the Add a new Group pop-up in the non-Enterprise version.
- Upgraded to tshark 1.6.9 to resolve some security vulnerabilities.
- When viewing a capture file the Direct Access link in the Sharing tab of the Info pop-up now lists https style links if https is enabled on the appliance.
- The Comments tab of the Info pop-up now uses a fixed width font.
- Resolved an issue with && display filters. These style display filters were not being properly encoded in previous releases.
- The optional filename argument is now supported when calling the API upload method using an HTTP POST.