Hi Andy,
Thank you for your reply! I am CC'ing Lei on mine.
On Wed, May 20, 2015 at 12:55:10PM +0200, Andy Polyakov via RT wrote:
For reference. icc was not cared for for quite some time. Initially it
was possible for me, by then university employee, to use it, but then
they changes terms
Hi,
Lei Zhang (re)discovered that OpenSSL 1.0.1* and below gets miscompiled,
resulting in incorrect computation of at least SHA-1 hashes (and probably
SHA-0, MD4, MD5) when it's compiled with icc for 64-bit Linux (x86_64 or
mic), but not for Windows. The problem is already fixed in 1.0.2 and in
Hi,
I've noticed this while reviewing diffs between 0.9.6h and 0.9.6i:
--- openssl-0.9.6h/crypto/x509/x509_vfy.c Thu Nov 28 11:06:30 2002
+++ openssl-0.9.6i/crypto/x509/x509_vfy.c Tue Dec 10 11:28:16 2002
@@ -897,7 +897,7 @@
ctx-chain=NULL;
}
Sorry for following up on my own mail, but I just wanted to say that
reverting the change now seems right to me (it's setting ex_data-sk
to NULL, not zeroing out sensitive data).
On Thu, Feb 20, 2003 at 10:06:55AM +0300, Solar Designer wrote:
Hi,
I've noticed this while reviewing diffs
to our package which could be relevant is this:
* Wed Sep 25 2002 Solar Designer [EMAIL PROTECTED]
- Don't do an explicit make build-shared, it's not needed and could only
cause harm (link libssl against libcrypto statically), but luckily didn't;
pointed out by Dmitry V. Levin of ALT Linux.
Basically
On Fri, Nov 15, 2002 at 09:05:13AM +0100, Richard Levitte - VMS Whacker via RT wrote:
rt # DIRS= crypto ssl rsaref $(SHLIB_MARK) apps test tools
rt # all: clean-shared Makefile.ssl sub_all
rt make Makefile.ssl
rt make sub_all DIRS=crypto ssl rsaref
rt LD_LIBRARY_PATH=`pwd` make sub_all
On Fri, Nov 15, 2002 at 09:05:13AM +0100, Richard Levitte - VMS Whacker via RT wrote:
rt # DIRS= crypto ssl rsaref $(SHLIB_MARK) apps test tools
rt # all: clean-shared Makefile.ssl sub_all
rt make Makefile.ssl
rt make sub_all DIRS=crypto ssl rsaref
rt LD_LIBRARY_PATH=`pwd` make sub_all
to our package which could be relevant is this:
* Wed Sep 25 2002 Solar Designer [EMAIL PROTECTED]
- Don't do an explicit make build-shared, it's not needed and could only
cause harm (link libssl against libcrypto statically), but luckily didn't;
pointed out by Dmitry V. Levin of ALT Linux.
Basically
JFYI, when updating our package from 0.9.6c to 0.9.6d I've noticed
that the new shared libcrypto library doesn't work anymore. The
openssl(1) binary wouldn't recognize any of the block ciphers. I
tracked this down to the addition of -Wl,-Bsymbolic. Removing that
option solved the problem for
JFYI, when updating our package from 0.9.6c to 0.9.6d I've noticed
that the new shared libcrypto library doesn't work anymore. The
openssl(1) binary wouldn't recognize any of the block ciphers. I
tracked this down to the addition of -Wl,-Bsymbolic. Removing that
option solved the problem for
On Mon, Apr 29, 2002 at 03:48:48PM +0100, Ben Laurie wrote:
Solar Designer wrote:
it could also be nice to report the filename and strerror(errno), or
it is sometimes not immediately clear what the error messages apply to:
jill!solar:~/build/openssl-SNAP-20020416$ apps/openssl dgst -md5
On Tue, Apr 23, 2002 at 12:09:14PM +0100, Ben Laurie wrote:
Solar Designer wrote:
This sounds like a bug to me. Noticed it last year and I've just
checked that it's still not resolved in the latest snapshot.
jill!solar:~/build/openssl-SNAP-20020416$ apps/openssl dgst -md5 /bin/ls
MD5
Hi,
This sounds like a bug to me. Noticed it last year and I've just
checked that it's still not resolved in the latest snapshot.
jill!solar:~/build/openssl-SNAP-20020416$ apps/openssl dgst -md5 /bin/ls
MD5(/bin/ls)= d93498d9f52c3dc0330ab930fe3ffc50
OK.
13 matches
Mail list logo