Please see decrypted private key
http://pastebin.com/DzYLnHZT
On Mon, Apr 2, 2012 at 11:08 PM, Wim Lewis via RT r...@openssl.org wrote:
On 2 Apr 2012, at 10:21 AM, Tamir Khason via RT wrote:
Please see attached good and bad example + plain dump for both
The attached file was corrupted at
Le 03/04/2012 09:38, Tamir Khason via RT a écrit :
Please see decrypted private key
http://pastebin.com/DzYLnHZT
Thanks.
You didn't provide information on where you think the error is,
precisely. I'll base my answer on your previous posts.
You started to say that the coefficients should be
Le 03/04/2012 09:38, Tamir Khason via RT a écrit :
Please see decrypted private key
http://pastebin.com/DzYLnHZT
Thanks.
You didn't provide information on where you think the error is,
precisely. I'll base my answer on your previous posts.
You started to say that the coefficients should be
It seemed that we are speaking about different things.
In certificate i pasted, integers used for exponent1, exponent2 and
coefficient encoded with different lengths. In chapter 8.3 of ISO 8825
there is clear statement of how integer values should be encoded. All
need is to take those numbers from
On 04/03/2012 11:34 AM, Tamir Khason via RT wrote:
It seemed that we are speaking about different things.
In certificate i pasted, integers used for exponent1, exponent2 and
coefficient encoded with different lengths. In chapter 8.3 of ISO 8825
there is clear statement of how integer values
Erwann, Peter
This is right, but all numbers are integers and should be encodeed
accordingly. If encoding assuming fixed size integers, it should use
length octets, if not end-of-contents octets. At least this is how i
read 8.1 from ASN.1 spec
maybe i am failed to explain myself.
DER encoding says how to encode numbers, RSA key elements define what
are those number. So integers from RSA key, should be encoded
according ANS1 DER encoding, which means should be have either length
octets or end-of-contents octets
On Mon, Apr 2, 2012 at
This bug is present in OpenSSL 1.0.1 and all previous version which I
have looked at
Example of bug:
openssl ocsp -issuer tom-ca_root_cert.pem -nonce -CAfile
tom-ca_root_cert.pem -url
http://[2001:420:40ff:ffe0:bca9:7919:9219:86b6]:88 -cert
user_signed_cert.pem
Error connecting BIO
Error
I've realised that my proposed patch doesn't strip out the square
brackets from the host.
It probably needs to do that too.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
On 04/03/2012 11:34 AM, Tamir Khason via RT wrote:
It seemed that we are speaking about different things.
In certificate i pasted, integers used for exponent1, exponent2 and
coefficient encoded with different lengths. In chapter 8.3 of ISO 8825
there is clear statement of how integer values
On 3 Apr 2012, at 2:34 AM, Tamir Khason via RT wrote:
It seemed that we are speaking about different things.
In certificate i pasted, integers used for exponent1, exponent2 and
coefficient encoded with different lengths.
Yes. This is OK. In fact, it is required by DER (ISO 8825, etc).
In
Andy has made some recent fixes to the AES code too which may be
relevant. Please check the next snapshot to see if you still have problems.
I get the same results with openssl-1.0.1-stable-SNAP-20120403.tar.gz
To narrow down the problem, I built the no-asm version, (which works),
saved off
On 03/23/2012 07:52 AM, Stephen Henson via RT wrote:
[rouss...@measurement-factory.com - Wed Mar 21 10:24:07 2012]:
A verification callback registered with SSL_CTX_set_verify() gets
called for most validation errors, as expected. The callback always
returns 1 (keep validating) result so
13 matches
Mail list logo