Hi, I posted a week ago a message about smime segfault.
With the latest snap, openssl-SNAP-20020224, it doesn't segfault
anymore; instead for the sign command:
openssl smime -sign -in test.txt -text -signer cacert.pem -inkey
cakey.pem -out test_SMIME.msg
it replies with
No signer
Is there any reason why gcc -print-prog-name=collect2 is used for
detecting the linker instead of gcc -print-prog-name=ld? As far as I
know collect2 isn't actually used when linking c code. I've come
across a system where gcc -print-prog-name=ld points to the vendor
linker and gcc
From: Tim Rice [EMAIL PROTECTED]
Hi Tim,
I'm looking at your patch and have a few comments:
tim I've added -lresolv so it can find strcasecmp().
Cool, I'll fix that.
tim UnixWare 2.0x does not have strings.h so I changed apps.c and ca.c
tim ...
tim # ifdef NO_STRINGS_H
tim int
On Tue, 26 Feb 2002, Richard Levitte - VMS Whacker wrote:
From: Tim Rice [EMAIL PROTECTED]
tim UnixWare 2.0x does not have strings.h so I changed apps.c and ca.c
tim ...
tim # ifdef NO_STRINGS_H
tim intstrcasecmp();
tim # else
tim #include strings.h
tim #
Ok, It seems that for smime -sign it works but only with changes in smime.c
(in section
#ifndef OPENSSL_NO_AES
else if (!strcmp(*argv,-aes128))
cipher = EVP_aes_128_cbc();
else if (!strcmp(*argv,-aes192))
Jeffrey Altman wrote:
When compiling an application with OPENSSL_LOAD_CONF defined, the
macro maps to OPENSSL_add_all_algorithms_conf(), which additionally
calls OPENSSL_config(NULL). This will automatically load the
openssl.cnf file for engine configuration. The idea behind all this
Where is the openssl.cnf file expected to be found on Windows?
The actual location is now determined by the function
CONF_get1_default_config_file() and the openssl utility will be modified
so everything goes through it.
Currently this follows the same logic for finding openssl.cnf
Jeffrey Altman wrote:
Where is the openssl.cnf file expected to be found on Windows?
The actual location is now determined by the function
CONF_get1_default_config_file() and the openssl utility will be modified
so everything goes through it.
Currently this follows the same
But most applications will share the same config file settings, at least
as far as ENGINEs are concerned.
It isn't really appropriate to provide a function to set the config file
location. OPENSSL_config() is meant as a simple solution for existing
applications and it does rather horrible
Lutz Jaenicke [EMAIL PROTECTED]:
On Wed, Feb 20, 2002 at 12:29:03PM +0200, Yoram Zahavi wrote:
My server application is using SSL_clear to reuse the SSL object, instead of
allocating a new one on every new connection. On first connection the client
succeeds to connect the server, and later
10 matches
Mail list logo
