In message <[EMAIL PROTECTED]> on Sun, 8 Dec 2002 18:34:44 +0100, "Dr.
Stephen Henson" <[EMAIL PROTECTED]> said:
steve> I've got an ASN1 module that handles attribute certificates but
steve> hasn't been made publically available yet. Want a copy?
Uhmm, sure, but why not just commit it? If nothi
On Wed, Feb 20, 2002 at 06:45:41PM +0100, Richard Levitte - VMS Whacker wrote:
[...]
> If you look in conf.h, you'll also see why it includes e_os.h: an
> #ifndef NO_FP_API.
>
> BTW, in 0.9.7-dev, we have the same (or almost, it depends on
> OPENSSL_NO_FP_API) #ifndef, but that one is meaningles
From: Bodo Moeller <[EMAIL PROTECTED]>
moeller> The problem with 0.9.6-stable is that '#include ' was
moeller> added to conf.h, being automatically included by
moeller> x509v3.h. I consider this a bug: Writing '#include '
moeller> in the application sourcecode does not mean that you want an EXI
On Wed, Feb 20, 2002 at 03:07:16PM +0100, [EMAIL PROTECTED] wrote:
> Log:
> Including openssl/e_os.h in the OpenSSL 0.9.6 branch is legal, since
> it's exported. Changing that is a BIG step, which has been done in
> 0.9.7-dev.
>
> Revision ChangesPath
> 1.214 +1 -5 o
On Tue, Sep 25, 2001 at 01:34:51PM +0100, Ben Laurie wrote:
> [EMAIL PROTECTED] wrote:
>> 'openssl speed' does not include AES support yet
> It does if you use an EVP.
The at least the usage output should be corrected:
$ ./openssl speed foo
Error: bad option or value
Available values:
md2
[EMAIL PROTECTED] wrote:
>
> bodo25-Sep-2001 12:30:17
>
> Modified:.STATUS
> Log:
> 'openssl speed' does not include AES support yet
It does if you use an EVP.
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html
"There is no limit to what a man can do or how far he
On Thu, Jan 11, 2001 at 01:34:07PM +, Dr S N Henson wrote:
+o crypto/ex_data.c is not really thread-safe and so must be used
+ with care (e.g., extra locking where necessary, or don't call
+ CRYPTO_get_ex_new_index once multiple threads exist).
+
Bodo Moeller wrote:
>
> On Wed, Jan 10, 2001 at 06:11:57PM +, Dr S N Henson wrote:
> > [EMAIL PROTECTED] wrote:
>
> >> +o crypto/ex_data.c is not really thread-safe and so must be used
> >> + with care (e.g., extra locking where necessary, or don't call
> >> + CRYPTO_g
On Wed, Jan 10, 2001 at 06:11:57PM +, Dr S N Henson wrote:
> [EMAIL PROTECTED] wrote:
>> +o crypto/ex_data.c is not really thread-safe and so must be used
>> + with care (e.g., extra locking where necessary, or don't call
>> + CRYPTO_get_ex_new_index once multiple threa
[EMAIL PROTECTED] wrote:
>
>
> +o crypto/ex_data.c is not really thread-safe and so must be used
> + with care (e.g., extra locking where necessary, or don't call
> + CRYPTO_get_ex_new_index once multiple threads exist).
> + The current API is not suitable for ever
rse> - o Solaris 2.6Ralf S. Engelschall ctype warns, test fails in
test_ssl
I nkow you've fixed the test_ssl problem. For the ctype warns, it
seems like the following works (at least it does for me. Solaris 2.6,
gcc 2.8.1). I have *not* put this code through DEC C (versino 6.
>The best way is to talk Peter Gutmann into donating his randomness-gathering
>code (or to implement something similar). For efficiency that should
>probably be combined with a seed file.
This has already been done so it could be used with GPG (actually it's always
been available for the asking,
>>> +o Properly initialize the PRNG in the absence of /dev/random.
>
>> How?
>
>Perhaps the same ugly but useable way Eric fiddles around in the randfile.c
>source. He just reads the whole size buffer although he knows that he only has
>put less data in. Or like mod_ssl which reads out the s
13 matches
Mail list logo
