[openssl-dev] [openssl.org #4682] PKITS tests fails with 1.0.2i on GNU/Linux

2016-09-22 Thread Bruce Stephens via RT
The problem appears to be 325da823, x509_vfy.c line 1132. best_score starts at 0 (from get_crl_delta's crl_score, initialised to 0), and (for whatever reason) crl_score also turns out to be 0. So if (ASN1_TIME_diff(, , X509_CRL_get_lastUpdate(best_crl),

[openssl.org #2741] [PATCH] 1.0.1-beta3 fails to build on Windows if --with-fipsdir is used

2012-02-28 Thread Bruce Stephens via RT
ms/nt.mak and ms/ntdll.mak end up with FIPSDIR=C:\\ BASEADDR=... and the trailing \ quotes the line ending. Or something, anyway it doesn't work. I didn't notice that earlier because I send an incorrect suggestion for PR: 2708; mine changed just the first / which isn't what was

[openssl.org #2727] [PATCH] bashism in crypto/srp/Makefile

2012-02-22 Thread Bruce Stephens via RT
If EXHEADER is set to empty, make install will fail on some platforms. This is fixed in most subdirectories and this just copies the fix to srp. --- a/crypto/srp/Makefile +++ b/crypto/srp/Makefile @@ -43,7 +43,8 @@ links: @$(PERL) $(TOP)/util/mklink.pl ../../apps $(APPS) install: -

[openssl.org #2708] 1.0.1beta2 fipsdir is changed incorrectly in util/mk1mf.pl

2012-02-09 Thread Bruce Stephens via RT
At line 62: $fipsdir =~ tr/\//${o}/; But that's before the platform file has been loaded, so $o hasn't been set. And tr doesn't do variable expansion, so this won't work anyway. Using s rather than tr and moving it down the file (after the platform file has been loaded, so line 236 or

Re: [openssl.org #2639] Resolved: When running pkits-test.pl on 1.0.0e or trunk, three tests fail

2011-12-14 Thread Bruce Stephens via RT
Stephen Henson via RT r...@openssl.org writes: According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. I see a related change, to permit use of the old PKITS (with now expired trust anchor). However, the three

Re: [openssl.org #2639] Resolved: When running pkits-test.pl on 1.0.0e or trunk, three tests fail

2011-12-14 Thread Bruce Stephens via RT
Stephen Henson via RT r...@openssl.org writes: According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. I see a related change, to permit use of the old PKITS (with now expired trust anchor). However, the three

Re: [openssl.org #2639] Resolved: When running pkits-test.pl on 1.0.0e or trunk, three tests fail

2011-12-14 Thread Bruce Stephens via RT
Stephen Henson via RT r...@openssl.org writes: According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. I see a related change, to permit use of the old PKITS (with now expired trust anchor). However, the three

Re: [openssl.org #2639] When running pkits-test.pl on 1.0.0e or trunk, three tests fail

2011-12-14 Thread Bruce Stephens via RT
Stephen Henson via RT r...@openssl.org writes: [...] As I indicated there were problems with the PKITS data itself, not OpenSSL. The test data has now been updated (see message from David Cooper in PKITS mailing list). Try downloading it again from NIST site. OK, thanks. I thought that might

[openssl.org #2639] When running pkits-test.pl on 1.0.0e or trunk, three tests fail

2011-11-11 Thread Bruce Stephens via RT
4.3.10 Valid Rollover from PrintableString to UTF8String Test10 : Failed! Filename: pkits/smime/SignedValidRolloverfromPrintableStringtoUTF8StringTest10.eml Return code:52, expected 0 Command output: WARNING: can't open config file: /usr/local/ssl/openssl.cnf Verification failure

[openssl.org #2247] Unsafe (unnecessary?) code in crypto/perlasm/x86_64-xlate.pl

2010-04-28 Thread Bruce Stephens via RT
This check seems not to work as intended on one of our Windows 64 machines (a VM we use for building releases, as luck would have it): { my ($stddev,$stdino,@junk)=stat(STDOUT); my ($outdev,$outino,@junk)=stat($output); open STDOUT,$output || die can't open $output: $! if

[openssl.org #1499] Uninitialized value in RAND_load_file, with -DPURIFY

2007-03-02 Thread Bruce Stephens via RT
If RAND_load_file is called with a non-NULL file which does not exist, then it still does: i=stat(file,sb); /* If the state fails, put some crap in anyway */ RAND_add(sb,sizeof(sb),0.0); if (i 0) return(0); And sb may well be uninitialized. Obviously that's of

[openssl.org #1228] openssl/sha.h requires sys/types.h, but does not include it

2005-10-25 Thread Bruce Stephens via RT
The following trivial C file fails to compile in 0.9.8a: #include openssl/sha.h void foo(void) { } In file included from test.c:1: /usr/include/openssl/sha.h:109: error: syntax error before 'size_t' /usr/include/openssl/sha.h:111: error: syntax error before 'size_t'