[[EMAIL PROTECTED] - Wed Jan 1 18:40:53 2003]:
> > > cl ... -c .\crypto\asn1\n_pkey.c
> > > .\crypto\asn1\n_pkey.c(96) : error C2370:
>'NETSCAPE_ENCRYPTED_PKEY_it' :
> > > redefinition; different storage class
> > > .\crypto\asn1\n_pkey.c(93) : see declaration of
> > > 'NETSC
In message <[EMAIL PROTECTED]> on Wed, 1 Jan 2003 06:11:24 -0800,
Kris Kennaway <[EMAIL PROTECTED]> said:
kris> uname -m returns "sparc64". I assume that the use of the hw.model
kris> sysctl is so different x86 CPUs can be distinguished for purposes of
kris> asm support (they all return "i386" f
Patch applied.
This ticket is now resolved.
[[EMAIL PROTECTED] - Tue Dec 31 16:42:29 2002]:
> The files.
> ./crypto/dsa/dsagen.c
> ./crypto/x509v3/v3conf.c
>
> seems no longer used (reference from makefiles). But some functions
> have
> wrong number of arguments. The files should IMHO be r
In message <02f301c2b1ea$4da5a480$[EMAIL PROTECTED]> on Thu, 2 Jan 2003 00:05:39
+0100, "Gisle Vanem" <[EMAIL PROTECTED]> said:
giva> "Richard Levitte - VMS Whacker" <[EMAIL PROTECTED]> said:
giva>
giva> > OK, this is very odd. Can you check against the two attached
giva> > archives? In those
"Richard Levitte - VMS Whacker" <[EMAIL PROTECTED]> said:
> OK, this is very odd. Can you check against the two attached
> archives? In those files, it looks like the result of your proposed
> patch.
No, the files in you attachment are wrong. It's quite simple;
'DSA_generate_parameters()' shou
In message <015701c2b1a4$1dcef310$[EMAIL PROTECTED]> on Wed, 1 Jan 2003 15:43:14
+0100, "Gisle Vanem" <[EMAIL PROTECTED]> said:
giva> "Richard Levitte - VMS Whacker" <[EMAIL PROTECTED]> said:
giva>
giva> > levitte> Please name it. The reason that I ask you is that the changes you
giva> > levitt
Andy Polyakov via RT wrote:
cl ... -c .\crypto\asn1\n_pkey.c
.\crypto\asn1\n_pkey.c(96) : error C2370: 'NETSCAPE_ENCRYPTED_PKEY_it' :
redefinition; different storage class
.\crypto\asn1\n_pkey.c(93) : see declaration of
'NETSCAPE_ENCRYPTED_PKEY_it'
> > > I'd be happy to unify them if you can guarantee they will never differ
> > > in any way that's important to us...
> >
> > "You" who? Me? I just wondered if it was possible as it does seem
> > unnecessary to *me* from first sight.
The sentence is confusing... First "it" above means "unified
> > cl ... -c .\crypto\asn1\n_pkey.c
> > .\crypto\asn1\n_pkey.c(96) : error C2370: 'NETSCAPE_ENCRYPTED_PKEY_it' :
> > redefinition; different storage class
> > .\crypto\asn1\n_pkey.c(93) : see declaration of
> > 'NETSCAPE_ENCRYPTED_PKEY_it'
>
> Strange, I checked VC++ 6.0 SP3 and
"Richard Levitte - VMS Whacker" <[EMAIL PROTECTED]> said:
> levitte> Please name it. The reason that I ask you is that the changes you
> levitte> propose are already present in 0.9.7 and 0.9.8-dev.
>
> Or is your patch a reverse patch?
No, not a reverse patch. The snapshot I diff'ed against was
Hi,
I have trouble running the following command with openssl version 0.9.7
openssl ca -policy policy_anything -out newcert.pem \
-passin pass:whatever -key whatever -extensions xpserver_ext \
-extfile xpextensions -infiles newreq.pem
It works fine with the 0.9.7-beta3 release but all later rele
In message <[EMAIL PROTECTED]> on Wed, 01 Jan 2003
15:19:23 +0100 (CET), Richard Levitte - VMS Whacker <[EMAIL PROTECTED]> said:
levitte> In message <009101c2b19e$766254a0$[EMAIL PROTECTED]> on Wed, 1 Jan 2003
15:02:44 +0100, "Gisle Vanem" <[EMAIL PROTECTED]> said:
levitte>
levitte> giva> "Rich
In message <009101c2b19e$766254a0$[EMAIL PROTECTED]> on Wed, 1 Jan 2003 15:02:44
+0100, "Gisle Vanem" <[EMAIL PROTECTED]> said:
giva> "Richard Levitte via RT" <[EMAIL PROTECTED]> said:
giva> >
giva> > Which OpenSSL version are you refering to?
giva>
giva> The latest SNAP-shot.
Please name it.
> rt> uname -m return on your machine? But most of all I wonder do we really
> rt> have to have separate lines for NetBSD, FreeBSD and OpenBSD? Why can't
> rt> we unify those lines to asteriskBSD-platform? In which case sparc64
> rt> recognition becomes a must as other flavors do support non-UltraS
On Wed, Jan 01, 2003 at 03:00:09PM +0100, Andy Polyakov wrote:
> > > I mean I see no reason why
> > > we should feel discouraged to recognize that it's sparc64. What does
> > > uname -m return on your machine? But most of all I wonder do we really
> > > have to have separate lines for NetBSD, FreeB
In latest 0.9.8 snapshot, some test-files include a protype for read().
Unfortunately this protype doesn't match the one in djgpp's .
Can we not removed this prototype?
The required system headers are included already I think.
Here is a patch to make it compile for djgpp:
--
"Richard Levitte via RT" <[EMAIL PROTECTED]> said:
>
> Which OpenSSL version are you refering to?
The latest SNAP-shot.
__
OpenSSL Project http://www.openssl.org
Development Mailing List
> > I mean I see no reason why
> > we should feel discouraged to recognize that it's sparc64. What does
> > uname -m return on your machine? But most of all I wonder do we really
> > have to have separate lines for NetBSD, FreeBSD and OpenBSD? Why can't
> > we unify those lines to asteriskBSD-platf
In message <[EMAIL PROTECTED]> on Wed, 1 Jan 2003 13:36:23 +0100
(MET), "Jeff A. Earickson via RT" <[EMAIL PROTECTED]> said:
rt> "man crle" on a Sun box. It is:
Not on the machine I currently have access to :-):
$ man crle
No manual entry for crle.
rt> crle - configure runtime linking envir
In message <[EMAIL PROTECTED]> on Wed, 1 Jan 2003 13:36:23 +0100
(MET), "Jeff A. Earickson via RT" <[EMAIL PROTECTED]> said:
rt> "man crle" on a Sun box. It is:
Not on the machine I currently have access to :-):
$ man crle
No manual entry for crle.
rt> crle - configure runtime linking enviro
In message <[EMAIL PROTECTED]> on Wed, 1 Jan 2003 14:13:55
+0100 (MET), "Andy Polyakov via RT" <[EMAIL PROTECTED]> said:
rt> uname -m return on your machine? But most of all I wonder do we really
rt> have to have separate lines for NetBSD, FreeBSD and OpenBSD? Why can't
rt> we unify those lines
In message <[EMAIL PROTECTED]> on Wed, 1 Jan 2003 14:13:55
+0100 (MET), "Andy Polyakov via RT" <[EMAIL PROTECTED]> said:
rt> uname -m return on your machine? But most of all I wonder do we really
rt> have to have separate lines for NetBSD, FreeBSD and OpenBSD? Why can't
rt> we unify those lines
On Wed, Jan 01, 2003 at 02:13:55PM +0100, Andy Polyakov via RT wrote:
>
> > > > This patch appears to fix it (I stole the OpenBSD-sparc64 config
> > > > target). OpenSSL builds and passes 'make test'.
> > >
> > > Looks not too bad. I'm a little worried with the following assumption, however.
>
> > > This patch appears to fix it (I stole the OpenBSD-sparc64 config
> > > target). OpenSSL builds and passes 'make test'.
> >
> > Looks not too bad. I'm a little worried with the following assumption, however.
>Can you be sure that it doesn't hit any 32-bit platform?
>
> FreeBSD does not s
"man crle" on a Sun box. It is:
crle - configure runtime linking environment
which determines the search path for dynamic libs. I had forgotten
that I had added /opt/openssl/lib to this path. When I was testing
0.9.7 in various forms, I installed it in /opt/openssl-0.9.7, but
forgot to add the
On Tue, Dec 31, 2002 at 08:00:52PM -0600, Kenneth R. Robinette wrote:
> I am getting an error with OpenSSL 0.9.7 when trying to generate a certificate. It
> appears that the uniqueIdentifier is no longer valid. Is this correct?
>From the FAQ:
-snip--snip--snip--snip--snip--snip--snip--snip--sni
On Wed, Jan 01, 2003 at 04:25:38AM +0100, Richard Levitte via RT wrote:
>
> [[EMAIL PROTECTED] - Tue Dec 31 13:23:43 2002]:
>
> > This patch appears to fix it (I stole the OpenBSD-sparc64 config
> > target). OpenSSL builds and passes 'make test'.
>
> Looks not too bad. I'm a little worried wi
Windows XP Professional SP1 with all updates.
I used:
perl Configure BC-32 no-idea no-mdc2 no-rc5
ms\do_nasm.bat
make -f ms\bcb.mak
The error:
bcc32 -otmp32\x_all.obj -Iinc32 -Itmp32 -DWIN32_LEAN_AND_MEAN -q
-w-aus -w-par -w-inl -c -tWC -tWM -DOPENSSL_SYSNAME_WIN32
-DL_E
The ASN1_TIME_to_generalizedtime() function in openssl 0.9.7
generates a \0-terminated string instead of Z-terminated.
Problem becomes apparent when making an openssl
ocsp server and client communicate. The client
gives a OCSP_R_ERROR_IN_THISUPDATE_FIELD error.
Frederik
diff -ur openssl-0.9
29 matches
Mail list logo
