> Shashank Khanvilkar wrote:
> > Yes.. i did use SSLdump, with the private RSA key to capture the trace.
> > Below is the command that i used.
> > /usr/local/sbin/ssldump -i eth0 -A -d -X -k
$HOME/certificates/client.pem
> > port
> >
> > I think ssldump has no option to dump the application
Shashank Khanvilkar wrote:
Yes.. i did use SSLdump, with the private RSA key to capture the trace.
Below is the command that i used.
/usr/local/sbin/ssldump -i eth0 -A -d -X -k $HOME/certificates/client.pem
port
I think ssldump has no option to dump the application data in hex.. but I
will che
>
> If you have access to the private RSA key, than you can get ssldump to
> decrypt the application data, see the ssldump man page for more
information.
> Ciao,
Yes.. i did use SSLdump, with the private RSA key to capture the trace.
Below is the command that i used.
/usr/local/sbin/ssldump -i et
Shashank Khanvilkar wrote:
Hi,
I don't know how to exactly describe my problem, but I will try my best with
the help of a packet trace.
Below is a trace of an SSL session. As seen from this, when the handshake is
complete, and i send an applicaion data of 128 bytes, why do i get
two record layer pa
Hi,
I don't know how to exactly describe my problem, but I will try my best with
the help of a packet trace.
Below is a trace of an SSL session. As seen from this, when the handshake is
complete, and i send an applicaion data of 128 bytes, why do i get
two record layer packet, instead of just one.