I hate buggy compilers! Building crypto/rand/rand_lib.c with -g flag fixes
the randtest problem and allows most of the tests to succeed. The treq fails
because openssl can't find subjectKeyIdentifier. Rebuilding crypto/x509v3
with -g clears this up. What a pain. (At this point the obvious thing
On Wed, Aug 28, 2002 at 02:22:02PM -0400, Ghanta, Bose wrote:
Dear Richard and the OpenSSL team,
I am very sorry for this delay. We have now got our legal review and
approval of the export license. We will be ready now to submit our changes
to OpenSSL organization to get it reviewed
FIPS PUB 180-2, which defines SHA-256, SHA-384 and SHA-512 in addition
to SHA-1, has been published on August 1:
http://csrc.nist.gov/publications/fips/fips180-2/fips180-2.pdf
These new hash algorithms should be added to the 0.9.8-dev branch.
On Thu, Aug 29, 2002 at 05:21:39PM +1000, Reddie, Steven wrote:
We have some code that was working with OpenSSL 0.9.6d this morning. Now
that I've upgraded to 0.9.6g it's failing.
OBJ_txt2nid(2.5.29.17) is now returning 0 instead of the expected 85
(NID_subject_alt_name).
We have some code that was working with OpenSSL 0.9.6d this morning. Now
that I've upgraded to 0.9.6g it's failing.
OBJ_txt2nid(2.5.29.17) is now returning 0 instead of the expected 85
(NID_subject_alt_name).
OBJ_nid2sn(NID_subject_alt_name) does return subjectAltName.
It seems that the
Can you elaborate what you think is buggy?
'make test' still succeeds if you substitute 10 for
SSL3_RT_MAX_PLAIN_LENGTH in ssl3_write_bytes (ssl/s3_pkt.c),
which sort of simulates very long certificate chains.
There is a limit to certificate chains (SSL_MAX_CERT_LIST_DEFAULT by
Please obtain OpenSSL 0.9.6g. OpenSSL 0.9.6d was the last version
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager
Thanks, the bug has been fixed now in 0.9.6-stable, 0.9.7-stable and
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List
hello Olaf
ich have the same problem with the
openssl bad serial number length
its also with the 2. request with my self -signed ca
but now i have suse 6.4 with 2.2.14
and there ich can't find the file ca.c
is there another way to solve the problem, probably installing another
version of
[EMAIL PROTECTED] via RT wrote:
hello Olaf
ich have the same problem with the
openssl bad serial number length
its also with the 2. request with my self -signed ca
but now i have suse 6.4 with 2.2.14
and there ich can't find the file ca.c
is there another way to solve the problem,
Hello folks,
Could anynody explain me the function CRYPTO_get_new_lockid() ?
Reading the source (0.9.6g engine) I only find that
there is a the name stored in a stack.
But no additional data for this ID is allocated.
So a later call to CRYPTO_lock with this ID results
in a access outside of
I've traced this down to ASN1_get_object. It fails at line 128 which had
previously been ifdef'd out:
if (*plength (omax - (p - *pp)))
{
ASN1err(ASN1_F_ASN1_GET_OBJECT,ASN1_R_TOO_LONG);
/* Set this so that even if things are not long
The bug is in OBJ_txt2obj at obj_dat.c:420. The 'i' in line:
op=d2i_ASN1_OBJECT(NULL,p,i);
should be replaced with 'j':
op=d2i_ASN1_OBJECT(NULL,p,j);
In the case of subject alt name (06 03 55 1D 11), i=3 and j=5. My guess is
that the code in ASN1_get_object which had
13 matches
Mail list logo
