Re: Doing a DH key exchange between OpenSSL and MS CryptoAPI

if you want to use different keys then u can implement a DH key exchange calling the openSSL DH crypto APIs. Bind , i think uses the OpenSSL crypto APIs. On 12/20/06, Edward Chan [EMAIL PROTECTED] wrote: Has anybody done this? I can get it to work when both ends are the same. But I can't do

[EMAIL PROTECTED]: Error while building openssl on ppc64 with gcc...]

Forwarded to openssl-users for discussion. Best regards, Lutz - Forwarded message from Atul Kulkarni (SIGSEC) [EMAIL PROTECTED] - X-Original-To: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Greylist: delayed 1563 seconds by postgrey-1.27

OpenSSL starttls example

Hi. I am implementing Jabber (XMPP) protocol and I need an example about acompleting the starttls procedure (as I understood - switch to secure tcp connection on existing unsecure one). I tried Google but couldnt find any example. Can someone supply me with it? Thanx. Alexander Semyonov

Re: OpenSSL starttls example

On 2007.01.11 at 15:11:46 +0200, Alexander Semyonov wrote: Hi. I am implementing Jabber (XMPP) protocol and I need an example about acompleting the starttls procedure (as I understood - switch to secure tcp connection on existing unsecure one). I tried Google but couldnt find any

Problems with ciphers (handshake failure)

Hi all, I am having problems using a certificate created with OpenSSL. I have created a PEM certificated with its private key using the next commands: - openssl genrsa -des3 -out Privatekey.pem 1024 - openssl req -new -x509 -key Privatekey.pem -out MyCertificate.pem -days 365 - openssl x509

Re: Problems with ciphers (handshake failure)

Hello, I am having problems using a certificate created with OpenSSL. I have created a PEM certificated with its private key using the next commands: - openssl genrsa -des3 -out Privatekey.pem 1024 - openssl req -new -x509 -key Privatekey.pem -out MyCertificate.pem -days 365 - openssl x509

Re: Make test: right shift test failed

Not that I got a response, but if anyone was paying attention (and for anyone who tries to google the problem as I did), I solved the problem by using gcc 3.3 to compile openssl instead of gcc 4.1. Dunno why it worked, but there you go. --Adam On Tue, 9 Jan 2007, Adam D. I. Kramer wrote: As a

FYI: OpenSSL engine. Cell / Playstation 3.

Hi all, I was asked to forward this to the list. I've been working on an OpenSSL engine to support the Cell processor's (Playstation 3 etc.) vector processors (SPU's) I've (finally!) got a rough version glued together using the IBM multi-precision library from the Cell SDK. You may be

FYI: OpenSSL engine. Cell / Playstation 3.

Hi all, I was asked to forward this to the list. I've been working on an OpenSSL engine to support the Cell processor's (Playstation 3 etc.) vector processors (SPU's) I've (finally!) got a rough version glued together using the IBM multi-precision library from the Cell SDK. You may be

RSA vs ECC: relative bruteforceability?

Hello openssl-users, I'm told that EC (elliptic curve) crypto with 256 bit keys may be as strong as the RSA with 16000 bit keys. Sounds incredible to me. Could someone please comment on this? Thank you in advance. -- Best regards, Anthony

Re: RSA vs ECC: relative bruteforceability?

On Fri, Jan 12, 2007 at 02:32:08AM +0300, ??? ?? wrote: Hello openssl-users, I'm told that EC (elliptic curve) crypto with 256 bit keys may be as strong as the RSA with 16000 bit keys. Sounds incredible to me.

garbage-in garbage-out - was OCSP response nonce extension encoding not DER

Looks like OpenSSL has a problem/feature of garbage-in garbage-out. It's a problem because it does not comply with the RFC and a feature because it lets OpenSSL work with broken clients. My OCSP request from some time ago had the encoding error of encoding the default values and it looks like