Re: function PEM_read_RSAPrivateKey not returning

Kyle Hamilton wrote: msvcr71d.dll? That looks like a debug version of the VC library to me. It was compiled and run in debug mode. Incidentally, I'm getting the same problem on VC8 (VC++2005 Express Edition). And I'm getting it even in release configuration. Somehow I am relieved and

OnReceive() not getting called

Hello, I have an FTPServer application developed using CAysncSocket, which is running quite well from the past 4 years. I have added SSL support to this application recently. This is how my application works exactly. A connection is established from a client. Once the connection (command

Re: function PEM_read_RSAPrivateKey not returning

On Thu, Feb 16, 2006, Matthias wrote: Somehow I am relieved and worried the same time that it affects not only me... I recently noticed a problem when attempting to use an OpenSSL DLL compiled against Visual Studio 2005 with an OpenSSL application compiled with another compiler. When both

Re: AES cipher

I tried adding : as suggested, but this still did not work. :( Does anyone have other suggestions? -Chris I'm trying to allow my program to be configurable for either AES 128 bit, or AES 256 bit. The problem is that when I select only the AES128-SHA cipher, the AES256-SHA cipher gets added

Which algorithms are need for PKCS12_parse?

I'm trying to use PKCS12_parse and it's failing with: error:06074079:digital envelope routines:EVP_PBE_CipherInit:unknown pbe algorithm error:23077073:PKCS12 routines:PKCS12_pbe_crypt:pkcs12 algor cipherinit error error:2306A075:PKCS12 routines:PKCS12_decrypt_d2i:pkcs12 pbe crypt error

Re: Which algorithms are need for PKCS12_parse?

On Thu, Feb 16, 2006, Chris wrote: error:06074079:digital envelope routines:EVP_PBE_CipherInit:unknown pbe algorithm error:23077073:PKCS12 routines:PKCS12_pbe_crypt:pkcs12 algor cipherinit error error:2306A075:PKCS12 routines:PKCS12_decrypt_d2i:pkcs12 pbe crypt error error:23076072:PKCS12

Re: Which algorithms are need for PKCS12_parse?

On 2/16/06, Dr. Stephen Henson [EMAIL PROTECTED] wrote: Its a password based encryption (PBE) algorithm. Probably 40 bit RC2 and/or3DES using the PKCS#12 key derivation algorihtm. Try calling PKCS12_PBE_add().Steve. Thanks! That did the trick. I wish all these _add() functions were listed

Cryptographic Hardware Accelerators for OpenSSL

Is it possible to add a new Hardware Accelerator beside those that are already supported as an Engine object in the OpenSSL implementation? My intent is trying to add as a new Engine some crypto modules from a Coldfire device..., but after reading some information and some links, it seem that it

Re: Cryptographic Hardware Accelerators for OpenSSL

On Thu, Feb 16, 2006, Lech Olmedo wrote: My intent is trying to add as a new Engine some crypto modules from a Coldfire device..., but after reading some information and some links, it seem that it is not possible... is this correct? I'm not sure what would make you think it isn't

Re: Which algorithms are need for PKCS12_parse?

On Thu, Feb 16, 2006, Chris wrote: On 2/16/06, Dr. Stephen Henson [EMAIL PROTECTED] wrote: Its a password based encryption (PBE) algorithm. Probably 40 bit RC2 and/or 3DES using the PKCS#12 key derivation algorihtm. Try calling PKCS12_PBE_add(). Steve. Thanks! That did the

Re: Cryptographic Hardware Accelerators for OpenSSL

I'm assuming it's also possible to statically link/bind (at build time) engine drivers. Is this the case? R. On Feb 16, 2006, at 3:50 PM, Dr. Stephen Henson wrote: On Thu, Feb 16, 2006, Lech Olmedo wrote: My intent is trying to add as a new Engine some crypto modules from a Coldfire

Re: Cryptographic Hardware Accelerators for OpenSSL

On Thu, Feb 16, 2006, Randy Turner wrote: I'm assuming it's also possible to statically link/bind (at build time) engine drivers. Is this the case? Yes. An application then would need to make an explicit call to the static engine code to either reference it explicitly or register it.

Re: Which algorithms are need for PKCS12_parse?

On 2/16/06, Dr. Stephen Henson [EMAIL PROTECTED] wrote: On Thu, Feb 16, 2006, Chris wrote:It is documented in doc/openssl.txt and that file is referred to in the FAQ...http://www.openssl.org/support/faq.html#MISC2 At some point I'll tidy that up and place it in an appropriate manual page orbetter

Re: function PEM_read_RSAPrivateKey not returning

I was using the precompiled binaries when that test failed. After I rebuilt the libraries with the VC8 compiler as Dr. Henson suggested, it worked. I consider it a bug in the Application Binary Interface of Windows, not a bug that OpenSSL can work around. -Kyle H On 2/16/06, Matthias [EMAIL

Re: AES cipher

Yeah. Any cipher that is not explicitly added is denied. So, try just doing: CString Shif = AES128-SHA; // C++ automatic type conversion converts Shif appropriately to LPSTR SSL_CTX_set_cipher_list(m_ctx, Shif); /* SSL_CTX_set_options(SSL_OP_NO_SSLv2); */ /* Since AES128 isn't an SSLv2 cipher

how to generate Private for Blowfish, CAST and rc4

Hi, I am using the 0.9.7e version of the openssl and i am having trouble with generating the private key for Blowfish, CAST and rc4. Was wondering how do i actually go about doing it. I have search the internet for any command lines related to them was unable to find any. Hope there is someone

openssl on arm

hi: I'm now trying to realize a SSL connection on embedded system.But I had some problems in the beginning.how can i compile the OpenSSL in arm-linux-gcc? Simple by changing thegcc to arm-linux-gcc in the Makefile? But i got the error as in the ScreenShot.png. how can i do with this ?