I also tried the same, and although wireshark labeled these data as
"encrypted application data", the text next to hex data in bottom window
contained unencrypted data. There were something added in the end, though.
(negotiated ciphersuite were NULL-SHA).
> 2) Getting back to the client & ser
On Thu, Jul 28, 2011 at 09:14:34AM -0700, navin gopalakrishnan wrote:
> 1) When i use my own applications (client & server) which uses
> the openssl library a separate client program and a separate server
> program, both configured to use only eNULL as above. (i.e. with only
> NULL_SHA & NULL_MD5)
___
From: Victor Duchovni
To: "openssl-users@openssl.org"
Sent: Wednesday, 27 July 2011, 20:20
Subject: Re: testing null encryption
On Wed, Jul 27, 2011 at 02:53:09AM -0700, navin gopalakrishnan wrote:
> a) testing NULL Encryption:
>
> While building openssl i modifi
On Wed, Jul 27, 2011 at 02:53:09AM -0700, navin gopalakrishnan wrote:
> a) testing NULL Encryption:
>
> While building openssl i modified the macro SSL_DEFAULT_CIPHER_LIST to
> #define SSL_DEFAULT_CIPHER_LIST "eNULL"
That was unwise, don't do that.
> My understan
Hi,
I am using openssl-1.0.0d. downloaded the source and built the library.
Can anyone suggest how to do the following:
a) testing NULL Encryption:
While building openssl i modified the macro SSL_DEFAULT_CIPHER_LIST to
#define SSL_DEFAULT_CIPHER_LIST "eNULL"
My understanding is
