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"))
cipher = EVP_aes_192_cbc();
else if (!strcmp(*argv,"-aes256"))
cipher = EVP_aes_256_cbc();
#endif
What about the smime -encrypt??? It seems that it SIGSEGV on
if(operation == SMIME_ENCRYPT) {
p7 = PKCS7_encrypt(encerts, in, cipher, flags);
}
Anyone any idea??
Regards,
Alex
alexandru matei wrote:
> 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 certificate specified"
>
> and for encrypt command
>
> "openssl smime -encrypt -in debug -to [EMAIL PROTECTED] -from
> [EMAIL PROTECTED] -subject OpenCA -des3 -out test_SMIME.msg 01.pem"
>
> with
>
> "unable to load certificate
> 30696:error:0906D06C:PEM routines:PEM_read_bio:no start
> line:pem_lib.c:627:Expecting: TRUSTED CERTIFICATE"
>
> Can anyone understand what is happening?
>
> PS. The snap was tested on RedHat 7.2 with ./config --prefix=/usr shared
> . Also I've tried to use 386 and no-asm in the config. All the tests
> were ended succesfully (on make test).
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> Development Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
