Andy Polyakov schrieb:
I actually ended up solving it by removing all uses of BIO_new_fp() in
favor of my own custom BIO that I just finished writing earlier this
week.
>>> Why not BIO_new_file?
>>
>> Yeah, I discovered while analyzing the code that using BIO_new_file()
>> rather th
Hello Andy,
Thank you very much for answering
Andy Polyakov a écrit :
If I have correctly understood the FAQ about the OPENSSL_applink. It
applies only in the Win32 version:
* If OPENSSL_USE_APPLINK is not defined at the compilation stage of
OpenSSL, the snippet applink.c is not man
> There was suggestion to fall back to wfopen from a vmware engineer a while
> ago, but he couldn't provide patch (not that it would be very complex) and
> it was not followed up. Idea must have been something similar to just
> committed http://cvs.openssl.org/chngview?cn=19610.
Sounds like a good
>>> When I use FIPS capable OpenSSL through Java JNI, I got error:
>>> "3392:error:2D06906F:FIPS
routines:FIPS_CHECK_INCORE_FINGERPRINT:fingerprint
>>> does not match nonpic relocated:.\fips\fips.c:236"
>>> which means it failed the base address check.
>>> Based on OpenSSL FIPS document, I changed
I actually ended up solving it by removing all uses of BIO_new_fp() in
favor of my own custom BIO that I just finished writing earlier this
week.
Why not BIO_new_file?
Yeah, I discovered while analyzing the code that using BIO_new_file()
rather than BIO_new_fp() would disengage applink, howeve
There is still a bug in the bitmask macros, reported by Daniel Mentz. While
checking if the message is complete a read might occur beyond the bitmask
array. This is fixed with this patch and the check is now also done backwards
which should be faster usually.
Regards,
Robin
--- ssl/d1_both.c
> I assume that it'll all end badly, but I won't know for a while.
Safe assumption, I suppose.
ALP $ search [...]*.h OPENSSL_SYSTEM
%SEARCH-I-NOMATCHES, no strings matched
ALP $ search [...]*.c OPENSSL_SYSTEM
**
ALP$DKA100:[UTILITY.SOURCE.OPENSSL.openssl-1^.0^.0-s
From: "Jouk Jansen"
> > http://antinode.info/ftp/openssl
> I tested the 1.0.0-s1 set from your web-page, but it has exactly the same
> problem when running the tests:
> [...]
> testing X509 conversions
> p -> d
> p -> n
> p -> p
> d -> d
> n -> d
> p -> d
> d -> n
> n -> n
> p -> n
> d -> p
Steven wrote on 16-APR-2010 17:14:47.36
>From: "Jouk Jansen"
>
>> When building OpenSSL on a OpenVMS machine, while "extended parse style is
>> on (i.e set proc/parse=extend) some of the tests fail. The solution is
>> simple : add a few double quotes in the command procedures. [...]
>
> Becaus
From: Andy Polyakov
> Even if somebody does, doesn't reporting it with VMS in subject decrease
> the chance of being taken care of? Yes, you've added HP-UX, but can you
> guarantee that my mail client didn't truncate it? BTW, it did:-)
45 characters is too many? And I thought that _I_ had
openssl-dev@openssl.org wrote on 16-APR-2010 17:14:47.36
>From: "Jouk Jansen"
[snip]
>> [...] I put the
>> "corrected" files on my web-page:
>>http://nchrem.tnw.tudelft.nl/openvms/software2.html#OSSL
>
> "0.9.8l" and "1.0.0-beta2" are hardly current. But don't worry.
>There are still ple
11 matches
Mail list logo
