RE: Is it not possible to decrypt partial AES messages?

2010-05-07 Thread Dave Thompson
> From: owner-openssl-us...@openssl.org On Behalf Of Steffen DETTMER > Sent: Wednesday, 05 May, 2010 14:04 > * Christina Penn wrote on Wed, May 05, 2010 at 07:42 -0400: > >Can you show me exactly how to break up my example code > to make my > >example work? I tried removing the EVP_Decryp

Re: PKCS12_parse() SEGV.

2010-05-07 Thread Dr. Stephen Henson
On Fri, May 07, 2010, David Woodhouse wrote: > On Fri, 2010-05-07 at 19:24 +0200, Dr. Stephen Henson wrote: > > Setting ca to NULL if it fails should work. That should be done in > > PKCS12_parse() on error. > > AIUI I don't want it to be NULL; I need it to be an empty stack. I need > the return

Re: PKCS12_parse() SEGV.

2010-05-07 Thread David Woodhouse
On Fri, 2010-05-07 at 19:24 +0200, Dr. Stephen Henson wrote: > Setting ca to NULL if it fails should work. That should be done in > PKCS12_parse() on error. AIUI I don't want it to be NULL; I need it to be an empty stack. I need the returned 'extra' certs so that I can work around RT#1942 on the

Re: PKCS12_parse() SEGV.

2010-05-07 Thread Dr. Stephen Henson
On Fri, May 07, 2010, David Woodhouse wrote: > With OpenSSL 0.9.8n this test program segfaults the second time it tries > to parse the PKCS#12 file. It was fixed for OpenSSL 1.0.0 by this > commit: http://cvs.openssl.org/chngview?cn=17957 > > Starting program: /home/dwmw2/p12test .cert/certificat

PKCS12_parse() SEGV.

2010-05-07 Thread David Woodhouse
With OpenSSL 0.9.8n this test program segfaults the second time it tries to parse the PKCS#12 file. It was fixed for OpenSSL 1.0.0 by this commit: http://cvs.openssl.org/chngview?cn=17957 Starting program: /home/dwmw2/p12test .cert/certificate.p12 Enter PKCS#12 passphrase: 140737353934504:error:23

Re: openssl enc block size

2010-05-07 Thread Johan van Selst
Johannes Bauer wrote: > > padding > Why would a 16 byte block need to be padded by one byte to 17 bytes? If you see an arbitary block of 16 bytes data it's hard to tell immediately whether the last byte is a padding element that should be removed or part of the content. That is why padding is _alw

Re: openssl enc block size

2010-05-07 Thread Dimitrios Siganos
Johannes Bauer wrote: Hello list, I'm having trouble with the openssl enc feature. This here: echo -n '0123456789abcde' | openssl enc -aes128 -nosalt -K 00112233445566778899aabbccddeeff -iv | wc -c (encoding 15 characters) results in one result block being gen

RE: openssl enc block size

2010-05-07 Thread PMHager
Johannes Bauer wrote on Friday, May 07, 2010 11:40: > (encoding 15 characters) results in one result block being generated ... > when encrypting a full block ... > Then two result blocks are generated ... PKCS#5 padding appends 1..blocksize padding bytes. -- Peter-Michael Hager - acm senior - H

Re: openssl enc block size

2010-05-07 Thread Johannes Bauer
Original-Nachricht > > padding Why would a 16 byte block need to be padded by one byte to 17 bytes? Regards, Johannes -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 _

Re: openssl enc block size

2010-05-07 Thread carlyoung
BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; } padding On Fri 07/05/10 10:39 AM , "Johannes Bauer" jb@gmx.de sent: Hello list, I'm having trouble with the openssl enc feature. This here: echo -n '0123456789abcde' | openssl enc -aes128 -nosalt -K 00112233445566778899aab

openssl enc block size

2010-05-07 Thread Johannes Bauer
Hello list, I'm having trouble with the openssl enc feature. This here: echo -n '0123456789abcde' | openssl enc -aes128 -nosalt -K 00112233445566778899aabbccddeeff -iv | wc -c (encoding 15 characters) results in one result block being generated: The command res