A lot of thanks, now roks perfectly.The problem it was that i put the commnad
line with -o and the correct form was:gcc -lssl -lcrypto cli.c
Thanks.
Date: Sat, 27 Feb 2010 11:33:31 -0800
From: pie...@hogranch.com
To: openssl-users@openssl.org
Subject: Re: Error copiling ssl: undefined
I am using AES_CBC with padding (using PKCS#5 to pad) on C++ side:
AES_set_encrypt_key( keyBuf, 128, key )
keyBuf contains key string
key is the key generated
Block Lenght is 16
AES_cbc_encrypt (ibuf, obuf, lenpad, key, iv, AES_ENCRYPT)
ibuf = input data
obuf = encrypted data
lenpad = length
Hello all !
How can I specify OpenSSL to use capi engine by default ???
(using openssl1.0.0beta5 library in my application)
__
OpenSSL Project http://www.openssl.org
User Support Mailing List
On Sun, Feb 28, 2010, ? wrote:
Hello all !
How can I specify OpenSSL to use capi engine by default ???
(using openssl1.0.0beta5 library in my application)
There are no default algorithm implementations in the CryptoAPI ENGINE at
present: just private key operations. If you load
Bruce Stephens wrote:
Dr. Stephen Henson st...@openssl.org writes:
[...]
Didn't realise anyone was using CFB for that.
Note - there is now a Debian bug logged too for encfs which appears to be
impacted by this change.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571810
I've
It doesn't make any difference in this case, but you'd be best to get in the
habit of putting the libraries last; for example
gcc cli.c -lssl -lcrypto
A few compilers only search libraries for references which they know about at
the time the library is listed. If you were using that sort of
