[openssl.org #46] buffer overflow in apps/ca.c & apps/req.c 0.9.7 snap 20020516

2002-05-27 Thread Stephen Henson via RT
Should be fixed now. __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]

[openssl.org #53] RE: Certificate

2002-05-27 Thread Lutz Jaenicke via RT
You may want to look into the details of the certificate and make sure, that the required trust settings are activated. It is not enough to simply have the certificate, but you also have to trust it. If this doesn't help, please ask this question on the openssl-users list. Best regards,

[openssl.org #54] Compilation error m68k-next-openstep4

2002-05-27 Thread Lutz Jaenicke via RT
Obviously in enginetest.c the strdup() -> BUF_strdup() migration was forgotten. I'll assign this to Richard, who takes care of the 0.9.6-engine branch. Best regards, Lutz __ OpenSSL Project

Re: openssl req -nameopt fails

2002-05-27 Thread Richard Levitte - VMS Whacker
Please make context diffs (-c) or even unified context diffs (-u). -- Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED] Redakteur@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47 \ SWEDEN \ or +46-708-26 53 44 Procurator Odiosus Ex Infernis-

Re: openssl req -nameopt fails

2002-05-27 Thread Michael Bell
Michael Bell schrieb: > So nameopt works if I used -subj but it fails for -text. I wrote a patch for req to support: -nameopt (for -text too) -reqopt Please read the README to see what I changed. Michael -- --- Michael Bell

openssl req -nameopt fails

2002-05-27 Thread Michael Bell
Hi, I test the following with "openssl req" /usr/local/ssl/bin/openssl req -in ie.pem -subject -noout [EMAIL PROTECTED]/CN=Roland Herbst/OU=Internet/O=Humboldt-Universitaet zu Berlin/C=DE /usr/local/ssl/bin/openssl req -nameopt RFC2253 -in ie.pem -subject -noout subject=C=DE,O=Humboldt-Univer

[openssl.org #56] Apparent bug in AES_ctr128_encrypt

2002-05-27 Thread Nick Mathewson via RT
The main loop from AES_ctr128_encrypt seems superficially incorrect. If any non-zero initial value is provided for "*num," the first 16-*num bytes are not necessarily encrypted. Also, the value for *counter is never used as provided, but is always incremented before use. For your reference,