If there's an easy way to decompress it, I certainly don't know it. Wireshark just gives me a pile of packets- I don't know what algorithm was used to compress the data, or even where the compressed data starts and ends.
Is there any documentation anywhere as to which SASL modules encrypt the data, vs. which don't? --- - Keith Palmer ConsoliBYTE, LLC Ask for a quote! - QuickBooks Integration and Software Development ke...@consolibyte.com 1-860-341-1464 http://www.ConsoliBYTE.com/ Follow us on Twitter at: https://twitter.com/consolibyte AIM: consolibyte MSN: supp...@consolibyte.com Yahoo: consolib...@yahoo.com Gtalk: consolibyte Skype: consolibyte On Feb 16, 2011, at 7:58 AM, Daniel Shahaf wrote: > No, I didn't mean it to sound harsh. I assumed that, having already > captured the data in wireshark, it would be straightforward to get > wireshark to decompress it or dump it to a file. > > Thanks for jumping in and correcting me. > > Daniel > > Julian Foad wrote on Wed, Feb 16, 2011 at 12:58:22 +0000: >> On Wed, 2011-02-16, Daniel Shahaf wrote: >>> Keith Palmer Jr. wrote on Tue, Feb 15, 2011 at 16:26:19 -0500: >>>> >>>> I tried to capture the traffic with Wireshark, but it appears that >>>> everything is compressed over the wire anyway... so I can't tell if >>>> I'm looking at just compressed data, or compressed+encrypted data. >>> >>> Decompress it then? >> >> Daniel, I'm sure you didn't mean that to sound harsh but it does to me! >> Decompressing it might be quite difficult to arrange, practically, and >> it was quite reasonable for Keith to enquire here before going to that >> effort. >> >> Thanks for your "depends on the SASL module" answer a few minutes later. >> >> - Julian >> >>
