Hi,
The big difference in the sign operation timings between the two keys is
not caused by any property of the second key parameters (like their
hamming weight) but it is rather the expected manifestation of two
counter-measures implemented by OpenSSL. Those are :
- RSA Blinding that prot
Just to add a data point to this discussion. There is a mechanism in OpenSSL
to avoid reencoding an ASN1 structure and to just cache the received encoding.
This is currently used in a few places already for various reasons. This has
an advantage in that it makes certificate verification quicker an
On 08/29/2010 07:38 PM, Mounir IDRASSI wrote:
Hi Peter,
Thank you for your comments.
As I said, this kind of debates can be very heated and going down this
road don't lead usually to any results.
The debate may be whether and how something should be
done in openssl, I admit I had started that
On 08/29/2010 01:20 PM, Mounir IDRASSI wrote:
Hi Peter,
Although the certificate's encoding of the serial number field breaks the
BER specification about the minimal bytes representation, it is known that
many CA's and libraries treat this field as a blob and usually encode it
on a fixed length
Could you please count the 1-bits in each exponent (e and d).
This might give an explanation.
-Original Message-
From: owner-openssl-...@openssl.org [mailto:owner-openssl-...@openssl.org] On
Behalf Of
Georgi Guninski
Sent: Sunday, August 29, 2010 10:51 AM
To: openssl-dev@openssl.org
Sub
Hello,
I would like to suggest a patch to ssl/s3_clnt.c (version 1.146) to
remove two erroneous comma expressions in that file.
--- s3_clnt.c.orig 2010-02-28 08:24:24.0 +0800
+++ s3_clnt.c 2010-08-28 22:36:25.0 +0800
@@ -1833,7 +1833,7 @@
if (n < 6)
Hi Thomas,
Thank you very much. I followed the guide and this issue has been solved.
--
View this message in context:
http://old.nabble.com/openssl-FIPS-on-linux-tp29477756p29553503.html
Sent from the OpenSSL - Dev mailing list archive at Nabble.com.
Hi Peter,
Although the certificate's encoding of the serial number field breaks the
BER specification about the minimal bytes representation, it is known that
many CA's and libraries treat this field as a blob and usually encode it
on a fixed length basis without caring about leading zeros.
Specif
The encoding is invalid BER.
The openssl is tolerant but also destructive in copy.
whenever you use openssl x509 -in -out ... you remove one leading 0 octet.
IMHO openssl should reject the cert because of invalid encoding.
On 08/29/2010 04:17 AM, Mounir IDRASSI wrote:
Hi,
The problem you a
inconsistent timings for rsa sign/verify with 100K bit rsa keys.
using pycrypto i generated two valid 100 000 bit rsa keys with the same modulus:
key1: log(n)=100K, e=2^16-1,d=BIG
key2: log(n)=100K, e=BIG, d=BIG
(note key1 and key2 share the same modulus)
recompiled openssl with increased parame
10 matches
Mail list logo
