Comments on: Sniffing SSL TLS Sessions with Wireshark http://www.bitplumber.net/2009/04/sniffing-ssl-tls-sessions-with-wireshark/ A place for Google to index my learnings Fri, 06 Jan 2012 08:18:20 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Alex Railean http://www.bitplumber.net/2009/04/sniffing-ssl-tls-sessions-with-wireshark/comment-page-1/#comment-9686 Alex Railean Mon, 08 Mar 2010 20:10:03 +0000 http://www.bitplumber.net/?p=290#comment-9686 Give a try to oSpy, it is a sniffer that allows you to view HTTPS traffic, provided that you're running it on Windows and the program that generates the traffic uses the Wincrypt API. It is not a universal tool, but for a subset of tasks it is exactly what one needs. Give a try to oSpy, it is a sniffer that allows you to view HTTPS traffic, provided that you’re running it on Windows and the program that generates the traffic uses the Wincrypt API.

It is not a universal tool, but for a subset of tasks it is exactly what one needs.

]]> By: Ruben http://www.bitplumber.net/2009/04/sniffing-ssl-tls-sessions-with-wireshark/comment-page-1/#comment-3679 Ruben Thu, 03 Sep 2009 08:55:56 +0000 http://www.bitplumber.net/?p=290#comment-3679 Not entirely true. You could sniff the client memory location; but that is not something that wireshark can do. See http://en.wikipedia.org/wiki/Diffie-Hellman_key_exchange#Description for more information about the genius of Diffie-helman. Not entirely true. You could sniff the client memory location; but that is not something that wireshark can do.

See http://en.wikipedia.org/wiki/Diffie-Hellman_key_exchange#Description for more information about the genius of Diffie-helman.

]]> By: Jörg Schulz http://www.bitplumber.net/2009/04/sniffing-ssl-tls-sessions-with-wireshark/comment-page-1/#comment-1390 Jörg Schulz Thu, 18 Jun 2009 10:32:06 +0000 http://www.bitplumber.net/?p=290#comment-1390 It's not possible to decrypt the DHE data. That's what DHE is for: secure key-exchange over unsecure channels. The only way to break this is by a MITM-attack, but that's not the way wireshark works. It’s not possible to decrypt the DHE data. That’s what DHE is for: secure key-exchange over unsecure channels. The only way to break this is by a MITM-attack, but that’s not the way wireshark works.

]]>