Wireshark QA

it made sense to break this out into a stand alone site and CloudShark.org was born. I am not going to debate the security concerns of sending a capture file into the cloud. This does not make sense in many cases. The security issue is true of many cloud applications. But there are a number of situations where having a browser based solution is extremely helpful. Consider the following ... 1) Web sites that host example capture files can now integrate those capture files into the browsing experience. This makes the capture file more accessible to anyone browsing the site. This is great for education and training sites. Take a look at what PacketLife has done with their capture examples. 2) Wireshark is not always available on every computing platform. For example， Thanks for the opportunity to shed some light on why we created CloudShark.org. We original developed the browser based decode idea to work with our own product CDRouter developed by QA Cafe. Once we saw this working with CDRouter， etc. Even if Wireshark does support the OS， CloudShark is not a complete replacement for running Wireshark locally. But the cloud concept does have merit to many situations where you need to look at a capture file. It is up to the user to decide when this is appropriate. ， smart phones， it may not be installed and you may not be allowed to install it. Consider a public terminal. In these situations， CloudShark is very helpful. 3) A CloudShark URL can point to a specific packet in a capture file and make linking very easy. This makes it easy to share a packet with a non-wireshark user. Most of the feedback we have received on CloudShark has been positive. Many security minded folks have pointed out the risk of sending capture files into the cloud. Certainly， iPads，。