Hi Steve,
I have compiled openssl with -DHAVE_CRYPTODEV -DUSE_CRYPTODEV_DIGESTS options.
My kernel is OCF enabled.
Below is the output of the command openssl asn1parse -genstr
OID:sha1WithRSAEncryption
# openssl asn1parse -genstr OID:sha1WithRSAEncryption
0:d=0 hl=2 l= 9 prim: OBJECT
# openssl smime -verify -in mail.smime -CAfile A-Trust-nQual-03.pem
Verification failure
3086427788:error:21071065:PKCS7 routines:PKCS7_signatureVerify:digest
failure:pk7_doit.c:1097:
3086427788:error:21075069:PKCS7 routines:PKCS7_verify:signature
failure:pk7_smime.c:410:
# openssl version
Hello list,
I need to compile a version of PPP that supports EAP-TLS
authentication protocol.
Fortunately there is a a patch that accomplishes exactly this [1].
I have built the package using the default libssl-dev package provided by my
operating system (Debian Wheezy/7.0). Specifically, it is
On Wed, Jun 26, 2013 at 02:57:15PM +0200, Marios Makassikis wrote:
By enabling debug information in the program, I was able to obtain
these error messages:
pppd[2236]: EAP-TLS SSL error stack:
pppd[2236]: error:0D0C5006:asn1 encoding routines:ASN1_item_verify:EVP lib
and
Hello,
On 26 June 2013 16:41, Viktor Dukhovni openssl-us...@dukhovni.org wrote:
On Wed, Jun 26, 2013 at 02:57:15PM +0200, Marios Makassikis wrote:
By enabling debug information in the program, I was able to obtain
these error messages:
pppd[2236]: EAP-TLS SSL error stack:
On Wed, Jun 26, 2013 at 05:29:52PM +0200, Marios Makassikis wrote:
By enabling debug information in the program, I was able to obtain
these error messages:
pppd[2236]: EAP-TLS SSL error stack:
pppd[2236]: error:0D0C5006:asn1 encoding routines:ASN1_item_verify:EVP
lib
and
This was tracked down to the makefile's `install` rule. The rule
builds components rather than only copying the executable and axillary
files.
The original `install` rule (fails the fingerprint check):
install: all install_docs install_sw
The modified `install` rule (passes the fingerprint
Hi,
I have the public and the private key for ECDSA on secp128r1 in a file
stored in PKCS8 format (saved with Crypto++; it is PKCS8 according to
the Docu).
I can create a signature without an error but unfortunately it is not
validated successfully with my Crypto++ app:
$ cat testakt.txt |
From: owner-openssl-us...@openssl.org On Behalf Of Lukas Haase
Sent: Tuesday, 25 June, 2013 19:13
I have the public and the private key for ECDSA on secp128r1 in a file
stored in PKCS8 format (saved with Crypto++; it is PKCS8 according to
the Docu).
I can create a signature without an
Hello,
Getting following error when trying to build openssl-1.0.1e for Win CE
Compiling using visual studio 2005 command prompt.
cl.exe /Fotmp32dll_X86\b_sock.obj -Iinc32 -Itmp32dll_X86 /MC /O1i /W3 /
WX /GF /Gy /nologo -DUNICODE -D_UNICODE -DOPENSSL_SYSNAME_WINCE -DWIN32_LEAN_AND
_MEAN
10 matches
Mail list logo