Using Tshark is pretty clever, though it exposes the CloudShark back end to the variety of vulnerabilities that get fixed with every new Wireshark release. For now, if you want to protect sensitive data in your capture files, don't use CloudShark. While the URLs to your decode session are not publicly shared, we make no claims that you data is not viewable by other CloudShark users. Apparently CloudShark renders the trace by invoking Tshark, then building the other Wireshark-like components separately. I generated the picture at right by downloading a trace showing FTP traffic from, then uploading it to CloudShark. Yesterday I learned of CloudShark, which looks remarkably similar to Wireshark but appears as a Web application. I've been interested in online packet tools for several years, dating back to my idea for, then continuing with Mu Dynamics' cool site, which I profiled in Traffic Talk 10.
0 Comments
Leave a Reply. |