Re: This is one for the Pros: cert is not privkey

(Since you top-posted, I will do so too in this thread) The certificate does not include the private key, only the public key. In a real (not test) setup you would use these like this: 1. Use the certificate file alone on any computer to encrypt data using theopenssl cms or openssl pkcs7

thread-safety questions on 1.0.1c

I am seeing lots of errors whose error message reads S server_ip: 2851965808:error:14092105:SSL routines:SSL3_GET_SERVER_HELLO:wrong cipher returned:s3_clnt.c:963: if I run it in at least several (8+) threads. Single threaded it's all doing fine, so I guess the kind of issue is obvious. I

EAP-TLS error: RSA_padding_check_PKCS1_type_1:block type is not 01

Hi All, I'm using Freeradius server2.1.12 on x86 fedora14. My client is using (armel ubuntu 10.04 lucid) IMX53 board. When I try connecting to radius server I am receiving the following errors. Do we require different certificates for arm boards, as I was able to run without any issues on

Re: EVP Padding size

So how do I fix this? -- View this message in context: http://openssl.6102.n7.nabble.com/EVP-Padding-size-tp42413p42447.html Sent from the OpenSSL - User mailing list archive at Nabble.com. __ OpenSSL Project

Re: This is one for the Pros: cert is not privkey

Peter Parker wrote: Dave, Thank you for the quick and thorough response. This is good stuff. Yes, so the files I will be encrypting will be over 100 bytes. I am aware of the key size requirements - 1028 was only used as a placeholder for the

RE: EVP Padding size

From: coderl [mailto:forumme5...@subdomain10.info] Sent: Wednesday, November 21, 2012 2:34 PM So how do I fix this? -- View this message in context: http://openssl.6102.n7.nabble.com/EVP- Padding-size-tp42413p42447.html You change whatever you're doing wrong and do it right instead. As

RE: linking error

From: Priyaranjan Nayak [mailto:priyaranjan4...@gmail.com] Sent: Thursday, November 22, 2012 2:36 PM While build the tls server I got this link error.Below I mentioned bild log . Can any one help me ? Linking console executable: bin/Debug/dtlsServer ../openssl-1.0.1c/libssl.a(ssl_algs.o):

RE: thread-safety questions on 1.0.1c

From: Thomas Eckert [mailto:thomas.eck...@sophos.com] Sent: Tuesday, November 20, 2012 9:44 AM I am seeing lots of errors whose error message reads S server_ip: 2851965808:error:14092105:SSL routines:SSL3_GET_SERVER_HELLO:wrong cipher returned:s3_clnt.c:963: if I run it in at least

EVP_Decrypt_Final_ex with Microsoft clients

Hi all, I'm working on an e-mail server written in node.js called Haraka. STARTTLS is supported in Haraka by use of the node.js crypto/TLS modules which wrap OpenSSL 1.0.0f + Chromium patches from Android. Last week I noticed some peculiarities on two clients that were sending e-mail to my

Re: EVP_Decrypt_Final_ex with Microsoft clients

On Thu, Nov 22, 2012, Steve Freegard wrote: Hi all, I'm working on an e-mail server written in node.js called Haraka. STARTTLS is supported in Haraka by use of the node.js crypto/TLS modules which wrap OpenSSL 1.0.0f + Chromium patches from Android. Last week I noticed some

Openssl - Bouncy Castle : Signature Verification Failure

I am trying to develop a java utility based on Bouncy Castle that should be able to sign and encrypt data which can later be decrypted and verified on the server side (openssl). Data encrypted by BC gets decrypted fine with Openssl Data signed by BC gets verified fine with Openssl But when I

Re: Openssl - Bouncy Castle : Signature Verification Failure

Its not exactly Signature Verification Failure. I get the following error - Error reading S/MIME message 24746:error:2107A083:PKCS7 routines:SMIME_read_PKCS7:invalid mime type:pk7_mime.c:364:type: application/octet-stream -- View this message in context: