Hi,
The X509V3_get_d2i never finds any extensions unless the idx argument is
NULL, which is not the intended behaviour. Here is a patch against
openssl-0.9.6g.
Regards,
Zoltan
Index: crypto/x509v3/v3_lib.c
===
RCS file:
Hi,
The OBJ_txt2obj does not call d2i_ASN1_OBJECT with the correct length
parameter, so that method always fails in openssl-0.9.6g (This used to work
in previous releases because the length checking was commented out in
d2i_ASN1_OBJECT). Please see the patch below.
Regards,
Zoltan
Index:
Welcome to the club. I also sent in for a patch for this one, and then
Stephen Henson told me that it had been fixed. It in CVS but not in any of
the official releases.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Zoltan Glozik
Sent: Monday, 23
Lutz Jaenicke wrote:
On Fri, Sep 20, 2002 at 10:34:27AM +0200, Bodo Moeller wrote:
On Thu, Sep 19, 2002 at 01:44:01PM +0200, Bodo Moeller via RT wrote:
I don't know why that message is empty. What I wrote is that this
should now be fixed in the current snapshots (0.9.6-stable and
0.9.8-dev
Chris Brook wrote:
Those of us who make heavy use of the crypto library, with a limited group
of algorithms and without SSL, would certainly not want this pulling in all
the algorithms every time we call EVP_PKEY_new.
What do you mean by pulling in? They get linked in anyway. And only
the
On Fri, Sep 20, 2002 at 06:19:48PM -0700, Patrick McCormick wrote:
Here's one step by step scenario.
You are absolutely right about the bug. I somehow had not realized
that the memcpy accesses the same struct as the following assignments.
We need a lock to fix this.
--
Bodo Möller [EMAIL
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
On Mon, Sep 23, 2002 at 04:26:00PM +0200, Bodo Moeller via RT wrote:
Somehow the RT2 system doesn't like the comments I enter at the
website when resolving a ticket ...
I wrote that the next snapshots should solve the problem. Functions
SSLv23_client_method(),
I am converting some code from BSAFE to OpenSSL, using 0.9.7 beta 3, and
have an issue with the PKCS#5 PBEParameters encoding/decoding. In BSAFE,
the algorithm ObjId is included in the PBEParameters encoding with an outer
SEQUENCE. In OpenSSL it is not. I can manually add strip off the algo
On Mon, Sep 23, 2002, Chris Brook wrote:
I am converting some code from BSAFE to OpenSSL, using 0.9.7 beta 3, and
have an issue with the PKCS#5 PBEParameters encoding/decoding. In BSAFE,
the algorithm ObjId is included in the PBEParameters encoding with an outer
SEQUENCE. In OpenSSL it is
10 matches
Mail list logo