Re: compilation failed because of rsa_oaep_test.c

In article [EMAIL PROTECTED] you wrote: Ralf S. Engelschall wrote: Was this file not committed? making apps... making test... make: don't know how to make rsa_oaep_test.o. Stop *** Error code 1 make links Oh shit, I forgot that this beast is the new one from crypto/rsa/. Sorry.

Re: Re: openssl

You'd probably better look at Cryptix if you neeed Java. Cryptix implements JCE only. There's no free SSL in Java... Maybe I'll be forced to use OpenSSL, though I don't think it's a good (=pure, portable) solution to build a .DLL and use it from Java. To come back to my previous email, I just

Re: undefined bn_div_words on alpha

On 22-Feb-99 Niels Poppe wrote: Peter Onion wrote: I just tried to build the snap shot on a Dec Alpha running RedHat 5.1. It failed I've not had time to look why yet... There is some unfinished work in the asm/alpha directories. I am no assembler demangler, but is seems this

[PATCH] SSLv3/TLSv1 identification bits

I've noticed that the new TLSv1 ciphers are not identified correctly by SSL_CIPHER_description() and this way they are also identified as "SSLv3" ciphers at the "openssl ciphers" command. The reason is because SSL_TLSV1 is currently defined to just the value of SSL_SSLV3. Because we've no more

Re: [PATCH] SSLv3/TLSv1 identification bits

Ralf S. Engelschall wrote: I've noticed that the new TLSv1 ciphers are not identified correctly by SSL_CIPHER_description() and this way they are also identified as "SSLv3" ciphers at the "openssl ciphers" command. The reason is because SSL_TLSV1 is currently defined to just the value of

Re: compilation failed because of rsa_oaep_test.c

Ben Laurie wrote: Ralf S. Engelschall wrote: Was this file not committed? making apps... making test... make: don't know how to make rsa_oaep_test.o. Stop *** Error code 1 make links I guess this got lost in the reshuffle, but we had made "make links" part of the configure

[PATCH] ssl-cert-xx_tmp_xx stuff lost

For a long time I've wondered myself why my Apache+mod_ssl development version still said "no shared ciphers" under DSA/DH situation while our OpenSSL s_server worked fine with the same DSA certificate/key files. After tracing down the problem I discovered that the ssl3_choose_cipher() function

ANSI-Style

Hi there, I have asked this before, but why are all the function headers writen in the old KR style? is that for compatibility with some compiler? It is not compatible with lxr and AFAICT this is doe to the non-ansi headers. I will asume that there are other source management tools out there

Re: cvs commit: openssl STATUS

+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 state of

Re: [PATCH] ssl-cert-xx_tmp_xx stuff lost

Ralf S. Engelschall wrote: In short, this (the s_server approach) works: ctx = SSL_CTX_new(); SSL_CTX_set_tmp_rsa_callback(ctx, ...); SSL_CTX_use_certificate(ctx, ...); ssl = SSL_new(); /* now ssl-cert contains the callbacks for the RSA temp key */ while this (the

Re: cvs commit: openssl STATUS

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,