I have a build script for some software that needs to locate the OpenSSL
headers and libraries, and I have reports that it is failing to locate
the libraries on some OSes.
One example identifies itself (via 'uname') as:
sunos open-solaris-noc 5.11 snv_95 i86pc i386 i86pc
What is the default
Victor B. Wagner wrote on 2009-10-19:
On 2009.10.19 at 16:30:14 +0100, Steve Hay wrote:
I have a build script for some software that needs to locate the
OpenSSL headers and libraries, and I have reports that it is failing
to
locate the libraries on some OSes.
One example identifies itself
How do I portably generate a random salt within a C program for use in
PKCS#5 v2.0 key derivation?
I find that just calling RAND_bytes() works OK on Win32 using 0.9.6 and
later, but not with 0.9.5. I can fix it by calling RAND_screen()
first. Is this OK? Do I also need to call RAND_screen()
Dr. Stephen Henson wrote:
On Fri, Sep 10, 2004, Dr. Stephen Henson wrote:
On Fri, Sep 10, 2004, Steve Hay wrote:
As an alternative to my luckless attempts at using
EVP_CIPHER_param_to_asn1() + PKCS5_v2_PBE_keyivgen(), I thought I would
try PKCS5_pbe2_set() + EVP_PBE_CipherInit
Dr. Stephen Henson wrote:
On Mon, Sep 13, 2004, Steve Hay wrote:
So now I'm back to square one: How do I do PKCS#5 key derivation using a
non-default key length?
Urk, yes you are right. There isn't a way to set the key length in
PKCS5_pbe2_set().
OK, I'd hoped to avoid this but I
Steve Hay wrote:
El hallabi-Kettani Abderrahmane wrote:
the function PKCS5_v2_PBE_keyivgen() exist in version
openssl0.7.9d in directory
openssl/crypto/evp/p5_crypt.c
it corresponds to what you want to do .
If you'd read my mail properly, you'd see that I'd already found
Dr. Stephen Henson wrote:
On Thu, Sep 09, 2004, Steve Hay wrote:
I've no idea what the ASN1_TYPE *param is, or where to get one from. I
had a look at EVP_CIPHER_param_to_asn1(), but it says that the cipher IV
in the ctx passed to it must be set when the call is made, which seems
Charles B Cranston wrote:
Perhaps one way to think of the IV is that it is part of the key.
That is, the IV and key are used to encrypt, and then the (same) IV
and the (same) key can decrypt.
IOW I could hard-code the IV into my source code, or use one supplied by
the user at build time (as
Dr. Stephen Henson wrote:
On Thu, Sep 09, 2004, Steve Hay wrote:
I'm afraid I don't know what password based encryption is, so I don't
know if this is the right thing to even be trying to do. It doesn't
sound like what I wanted...
It one of various standards which convert
Will Day wrote:
A short time ago, at a computer terminal far, far away, Steve Hay wrote:
I'm trying to build OpenSSL 0.9.5a on Solaris 2.4, using the Sun
WorkShop Compiler v3.0.
ar: asm/sparcv8.o cannot open
ar: asm/sparcv8.o not found
[...]
make this change in crypto/bn
10 matches
Mail list logo