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)
hi,
thanks for the info victor.
played with the openssl command line utility using the s_client & s_server
being configured to use eNULL with only NULL_SHA , NULL_MD5. The other ciphers
of eNULL are disabled.
I could see the client sending the above ciphers and the server selecting
NULL_SH
That didn't work. I immediately got an error from the server :
SSL3_GET_CLIENT_HELLO: no shared cipher.
Do you know what my original error meant:
SSL_BYTES_TO_CIPHER_LIST:scsv received when renegotiating
Maybe if I know what it is referring to I can track down the issue. There
isn't much po
It is for RSA keys.
Thanks,
Dirce
> Somewhere I have read that RSA key size limit is 32k or so. Largest key
> I have attempted to generate was 24k, largest key successfully
> generated and used was 16k. Are the these RSA keys or DH parameters?
> In any case 2048bit (2k) sized keys are supported
Thanks Wim, for your kind & informative answer.
Wim Lewis-3 wrote:
>
>
> On 26 Jul 2011, at 10:16 PM, Katif wrote:
>> Can you tell me what are the application dependency factor here so we'll
>> be
>> able to chase a limit?
>>
>> It is used as an RSA key exchange certification/private key p
Somewhere I have read that RSA key size limit is 32k or so. Largest key
I have attempted to generate was 24k, largest key successfully
generated and used was 16k. Are the these RSA keys or DH parameters?
In any case 2048bit (2k) sized keys are supported almost by anything.
> Hello,
> I am working
I'm using the PEM_write_X509(), avoiding the BIO, is there any difference?
Anyway, this function does not give errors.
Calling the ERR_error_string() on the failed verify, the error returned is:
error:0D0C5006:asn1 encoding routines:ASN1_item_verify:EVP lib
Searching on Google for this error it is
