0.9.8e: SIGILL in test tx509 (I have read the FAQ)
Hello, I'm running make test on openssl-0.9.8e built under linux and getting an illegal instruction in the tx509 test, both with and without the no-sse2 build option: $ bash -x ./tx509 + cmd='../util/shlib_wrap.sh ../apps/openssl x509' + '[' x '!=' x ']' + t=testx509.pem + echo testing X509 conversions testing X509 conversions + cp testx509.pem fff.p + echo 'p - d' p - d + ../util/shlib_wrap.sh ../apps/openssl x509 -in fff.p -inform p -outform d ./tx509: line 15: 26320 Illegal instruction $cmd -in fff.p -inform p -outform d f.d + '[' 132 '!=' 0 ']' + exit 1 My CPU has these flags: $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 44 model name : AMD Sempron(tm) Processor 3000+ stepping: 2 cpu MHz : 1808.372 cache size : 128 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow up pni lahf_lm ts fid vid ttp tm stc bogomips: 3620.08 clflush size: 64 My build configure line is: ./Configure no-idea no-rc5 enable-camellia shared linux-elf Any hints? __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
bug in base64 decode
http://lookit.typepad.com/lookit/2006/04/lame_openssl_bu.html Basically, openssl base64 -d silently fails if given a line longer than 79 characters. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
rsautl and smart card PIN on stdin
(opensc-0.10.0, openssl 0.9.8a, engine_pkcs11-0.1.3) Hi, I need to feed a PIN via stdin to openssl. The goal is to decrypt a file on disk and feed its result to some other script. I'm unsing this command: echo mypin | openssl rsautl -engine pkcs11 -in key.crypt -inkey 45 -keyform engine -decrypt -passin fd:0 Unfortunately this doesn't work: the pin is ignored and prompted for again: $ echo mypin | openssl rsautl -engine pkcs11 -in key.crypt -inkey 45 -keyform engine -decrypt -passin fd:0 reader-pcsc.c:495:pcsc_connect: SCardControl failed: Invalid parameter given. engine pkcs11 set. PKCS#11 token PIN: (no, I won't be using echo in this way, it's just to test stdin) Is this expected or a problem with openssl or the opensc pkcs11 engine? __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
Re: How to verify a pkcs7 detached signature?
On Fri, Jul 15, 2005 at 08:22:10AM +0200, Pablo J Royo wrote: Try this openssl smime -verify -in Assinador.tar.gz.pkcs7 -inform DER -content Assinador.tar.gz -signer signer_certificate.pem -noverify That works, thanks! __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
How to verify a pkcs7 detached signature?
1. http://www.iti.br/twiki/pub/Main/PressRelease2005Jun28A/Assinador.tar.gz 2. http://www.iti.br/twiki/pub/Main/PressRelease2005Jun28A/Assinador.tar.gz.pkcs7 [2] is supposed to be a detached signature for [1], how can this be verified with an openssl command? I was able to extract the certificate from the .pkcs7 file, but I hit a wall there. __ OpenSSL Project http://www.openssl.org User Support Mailing Listopenssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
