Re: [Wireshark-users] SSL Decryption on the Fly

2008-02-29 Thread Sake Blok
On Fri, Feb 29, 2008 at 10:17:44AM -0500, Robert D. Scott wrote: I am having trouble getting decrypted output. Debug Output: ssl_init keys string: 128.227.21.54,443,http,L:\2007\satst\satst.erp.ufl.edu.cer ssl_init found host entry 128.227.21.54,443,http,L:\2007\satst\satst.erp.ufl.edu.cer

Re: [Wireshark-users] SSL Decryption on the Fly

2008-02-29 Thread Robert D. Scott
: [Wireshark-users] SSL Decryption on the Fly On Fri, Feb 29, 2008 at 10:17:44AM -0500, Robert D. Scott wrote: I am having trouble getting decrypted output. Debug Output: ssl_init keys string: 128.227.21.54,443,http,L:\2007\satst\satst.erp.ufl.edu.cer ssl_init found host entry

Re: [Wireshark-users] SSL decryption

2008-02-04 Thread Al Aghili
SARAVANA PERUMAL RAMAKRISHNAN [EMAIL PROTECTED] writes: Hello,     I'm trying to collect soap traces using wireshark. The application is running in a solaris machine and i access the GUI for this application through a web browser in my windows PC. As soon as i enter the application

Re: [Wireshark-users] SSL Decryption

2007-08-10 Thread Derek Shinaberry
I've got it now. I knew I had to be missing something fundamental, because if I wasn't, the whole foundation of SSL would be in jeopardy. The pages I read talked about the client key exchange message sending the premaster secret from the client to the server, but neglected to mention that

Re: [Wireshark-users] SSL Decryption

2007-08-10 Thread Jeff Morriss
Well, remember, it's not *really* secure: Anybody with enough CPU time can break the encryption. And, what's worse, no one[1] can prove (or disprove) that the encryption is not breakable in much less time than is needed with brute force. [1] excepting those who purport that P=NP if P or N

Re: [Wireshark-users] SSL Decryption

2007-08-10 Thread Luis EG Ontanon
Is the following intelligent dominating species that's going to evolve in our planet after we go extint will be interested in what you encrypted? On 8/10/07, Jeff Morriss [EMAIL PROTECTED] wrote: Well, remember, it's not *really* secure: Anybody with enough CPU time can break the encryption.

Re: [Wireshark-users] SSL Decryption

2007-08-10 Thread Jeff Morriss
Nothing I've encrypted would be of interest, but if you're hiding from the all-seeing all-powerful NSA, maybe you'd care. [1,000 CPU years seems like a long time until you've got 10,000 CPUs working on the problem. 10,000 CPUs used to seem improbable but how many servers do they say Google

Re: [Wireshark-users] SSL Decryption

2007-08-10 Thread Luis EG Ontanon
If you are eavesdropping an ssl session you are not supposed to know the shared secret between the client and the server in order to avoid you decrypting what goes through client and server. The not allowing eavsdropers to see the clear text exchange between client and server happens to be the

Re: [Wireshark-users] SSL Decryption

2007-08-10 Thread Kukosa, Tomas
Hi, it is possible to decrypt the session if you retrieve somehow from client the master secret and some addtional information. There is not whole mechanism for it in the Wireshark now but there is function ssl_set_master_secret(). If you pass all necessary information to this function it can

Re: [Wireshark-users] SSL decryption

2007-08-06 Thread Stephen Fisher
On Mon, Aug 06, 2007 at 03:14:32PM -0400, Samson Katru wrote: Help me to decrypt ssl application data area 1. I have downloaded latest version of wireshark 0.99.6a 2. Server is mainframe..creates selfsigned server certificates. 3. Defined under preferneces ip,port,ssl,c:\server.kdb 4. trying

Re: [Wireshark-users] ssl decryption on Win32 (snakeoil example)?

2007-06-20 Thread Kukosa, Tomas
Hi, try to use absolute path to rsasnakeoil2.key (e.g. c:\ssl_example\rsasnakeoil2.key) to be sure that the right file is read. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon Polacheck Sent: Wednesday, June 20, 2007 7:55 PM To:

Re: [Wireshark-users] ssl decryption question

2006-12-06 Thread Joerg Mayer
On Wed, Dec 06, 2006 at 04:22:47PM +0100, Tatar Kolos wrote: Hi, Can anyone tell me what kind of problem is described in this ssldebug.log file? dissect_ssl3_handshake found SSL_HND_CLIENT_KEY_EXCHG state 17 ssl_decrypt_pre_master_secret key 17 diferent from KEX_RSA(16)

Re: [Wireshark-users] ssl decryption question

2006-12-06 Thread Tatar Kolos
Hi, On Wed, 6 Dec 2006, Joerg Mayer wrote: On Wed, Dec 06, 2006 at 04:22:47PM +0100, Tatar Kolos wrote: Hi, Can anyone tell me what kind of problem is described in this ssldebug.log file? dissect_ssl3_handshake found SSL_HND_CLIENT_KEY_EXCHG state 17 ssl_decrypt_pre_master_secret key

Re: [Wireshark-users] SSL Decryption Issues

2006-11-10 Thread Stephen Fisher
On Mon, Nov 06, 2006 at 11:00:26AM -0600, James Hughes wrote: Does anyone know why WireShark is loading 443 to HTTP, 636 to LDAP, 993 to IMAP and 995 to POP? I need 443 associated to something else. This is hard-coded in the source code: From epan/dissectors/packet-ssl.c:

Re: [Wireshark-users] SSL decryption -- RSA Key format

2006-11-01 Thread Vijay Sitaram
On Behalf Of Vijay SitaramSent: Friday, October 27, 2006 7:12 PMTo: Community support list for WiresharkSubject: Re: [Wireshark-users] SSL decryption -- RSA Key format Are you using Wireshark or the command line 'tshark' for this decryption? I have been trying to decrypt SSL traffic for the last coupl

Re: [Wireshark-users] SSL decryption -- RSA Key format

2006-10-27 Thread Kukosa, Tomas
I am not sure now if it is PKCS#8 but it has to be saved as only unencrypted privete key in PEM format. Regards, Tomas Od: [EMAIL PROTECTED] za uživatele Baker, Brian Odesláno: pá 27.10.2006 17:33 Komu: wireshark-users@wireshark.org Předmět:

Re: [Wireshark-users] SSL decryption problems

2006-10-07 Thread Jeff Sadowski
Well judging from the error message it seams the ssl plugin doesn't understand the keyword smtp. I noticed this when I was tring to do ssh. Try a different keywork for the protocal type. I'd try ssl On 10/7/06, Josh Kelley [EMAIL PROTECTED] wrote: I'm having some trouble getting SSL decryption