From: Claus Assmann [EMAIL PROTECTED]
ca+ssl-dev The signatures aren't accessible
ca+ssl-dev
ca+ssl-dev -rw--- Sep 24 16:37 openssl-0.9.6.tar.gz.asc
ca+ssl-dev -rw--- Sep 24 16:37 openssl-engine-0.9.6.tar.gz.asc
They are now, sorry about that.
--
Richard Levitte \ Spannvägen
Hi
i would like to know if the open ssl is platform independent
thanks
Roy
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated
From: "Peter Runestig (ECA)" [EMAIL PROTECTED]
peter.runestig --- ms/test.bat.origTue Mar 14 00:54:51 2000
peter.runestig +++ ms/test.bat Mon Sep 25 10:35:39 2000
peter.runestig @@ -1,4 +1,4 @@
peter.runestig -@echo=off
peter.runestig +@echo off
peter.runestig
peter.runestig set
peter.runestig --- ms/test.bat.orig Tue Mar 14 00:54:51 2000
peter.runestig +++ ms/test.bat Mon Sep 25 10:35:39 2000
peter.runestig @@ -1,4 +1,4 @@
peter.runestig -@echo=off
peter.runestig +@echo off
peter.runestig
peter.runestig set test=..\ms
peter.runestig set opath=%PATH%
From: "Peter Runestig (ECA)" [EMAIL PROTECTED]
peter.runestig ok, it's different between OS'es. "@echo=off" seems
peter.runestig equal to "@echo off" on NT4, but not on Win2000:
Thanks for the explanation. Committed.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
freebsd 2.2.5-RELEASE on an amd-300
gcc 2.7.2.1
OpenSSL 0.9.6 24 Sep 2000
built on: Mon Sep 25 07:40:05 GMT 2000
platform: FreeBSD
options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long)
idea(int) blowfish(idx)
compiler: gcc -DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486 -Wall
It magically worked once for me. But then when I try to rebuild the whole thing
from scratch, (unpack the source, apply the patch, update the .num file, do the
configuration with rc5 and idea turn off), it does not work again. The generated
libeay32.def still has the entry.
--
(~._.~) Öì Ⱥ Ó¢
From: zhu qun-ying [EMAIL PROTECTED]
qyzhu It magically worked once for me. But then when I try to rebuild
qyzhu the whole thing from scratch, (unpack the source, apply the
qyzhu patch, update the .num file, do the configuration with rc5 and
qyzhu idea turn off), it does not work again. The
Richard Levitte - VMS Whacker wrote:
I've placed mkdef.diff in ftp://ftp.stacken.kth.se/pub/random/levitte,
please apply it and try again. It also contains a corrected libray.num.
This one works smoothly with VC and mingw32.
Thanks.
--
(~._.~) Öì Ⱥ Ó¢ (Qun-Ying) (65) 874-6743
I wonder, is there any document somewhere that can tell us how the
different objects should really be named? As it currently looks, most
names are created ad-hoc.
I've just been hit with a problem where the naming of OID
1.2.840.113549.1.9.1 varies. When that is part of the CN rdn using
I just found RFC2253, so that one doesn't have to be pointed out to me
:-).
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \ SWEDEN \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis
I tried the hpux64-parisc2-cc with your patch applied to the 0924
snapshot. It fails like so,
some warnings early in the build:
cc: "ebcdic.c", line 1: warning 501: Empty source file.
as: "asm/pa-risc2W.s", line 1601: warning 8: Subspace characteristics may
not be changed after first definition
Hi
I think it's a great idea to give the OID's the correct names in objects.h.
I don't know if a document with the names exist, but when I want to know the
name associated to an OID, I always go to:
http://www.alvestrand.no/objectid/
I think you can find most of the OpenSSL predefined OID's
Richard Levitte - VMS Whacker wrote:
I wonder, is there any document somewhere that can tell us how the
different objects should really be named?
Currently there is no such central document since everybody is free
to define OIDs after getting a OID arc. Not even a central registry
exists.
From: "Hellan,Kim KHE" [EMAIL PROTECTED]
khe http://www.alvestrand.no/objectid/
khe
khe I think you can find most of the OpenSSL predefined OID's there
khe (including the names).
I know about alvestrand. Guess what? 1.2.840.113549.1.9.1 is named
"e-mailAddress" there.
Also, anyone can
Richard Levitte - VMS Whacker wrote:
I just found RFC2253, so that one doesn't have to be pointed out to me
:-).
But this does not help much with attribute type naming. It only
says:
-
If the AttributeType is in a published table of
My experience has been that you need to consult each standard separately.
RFC 2459 is good in that it includes object identifiers from a bunch of
standards, including the PKCS standards, and the X.5 standards (e.g., X.509
and X.520).
Frank
-Original Message-
From: Richard Levitte -
From: Michael **UNKNOWN CHARSET** [EMAIL PROTECTED]
michael Currently there is no such central document since everybody is free
michael to define OIDs after getting a OID arc. Not even a central registry
michael exists. For registering OIDs it's sufficient that the owner of the
michael parent
From: Frank Balluffi [EMAIL PROTECTED]
frankb My experience has been that you need to consult each standard
frankb separately. RFC 2459 is good in that it includes object
frankb identifiers from a bunch of standards, including the PKCS
frankb standards, and the X.5 standards (e.g., X.509 and
Michael Ströder wrote:
Currently there is no such central document since everybody is free
to define OIDs after getting a OID arc. Not even a central registry
exists.
No official central regitry, yes, but at least there is this non-official
one :
http://www.alvestrand.no/objectid/
It's
Jean-Marc Desperrier wrote:
Michael Ströder wrote:
Currently there is no such central document since everybody is free
to define OIDs after getting a OID arc. Not even a central registry
exists.
No official central regitry, yes, but at least there is this non-official
one :
Richard Levitte - VMS Whacker wrote:
But for example, the
"legal" shortnames for the DN attributes should be available
somewhere.
Can you list a limited set of attribute types for certificate DNs? I
can't.
I did find some in RFC2253, and I'm pretty sure there are
more in some X.500 or
For those who haven't see the following.
Date: Thu, 21 Sep 2000 01:11:27 -0700
To: OSI Directory List [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
From: "Hoyt L. Kesterson II" [EMAIL PROTECTED]
Subject: sixth revision of the draft 4th edition of X.509 is on the server
hello
On Mon, 25 Sep 2000, Michael Ströder wrote:
Jean-Marc Desperrier wrote:
No official central regitry, yes, but at least there is this
non-official one :
http://www.alvestrand.no/objectid/
Thank you. I already knew that one.
It's quite complete, while sure not comprehensive.
Richard Levitte wrote:
And still, short names have been used for a while, since they do appear
in
X.400 addresses and in DNs a little here and there.
Pardon me for butting in to the discussion this late, but is this really
an issue of short or long names?
I think the core problem at hand
Richard Levitte - VMS Whacker wrote:
But I guess that the right way would be to make it less humanly
readable and use the hash of the issuer DN, the same way it should be
done according to RFC2560...
RFC2560:
"issuerNameHash is the hash of the Issuer's distinguished name. The
hash shall be
In some cases one might want to set a string in an OpenSSL CONFIG object.
The following code does just that and it works for 0.9.5a but did not check
if it works for 0.9.6 release.
I used it extensively and thought that it might be useful for others but
presently
have no time to test and
On Mon, Sep 25, 2000 at 06:41:08PM +0200, Anton J. Gamel wrote:
Hi!
Who the hell removed the support for hpux 10 i.e.
NON-PARISC hardware with m68k??
file: config -- line 477
openssl 0.9.4 still allowed hpux-$CC.
openssl 0.9.5 and 0.9.6 force hpux-parisc-$CC
with many consequences.
On Mon, 25 Sep 2000, Richard Levitte - VMS Whacker wrote:
: To begin with, I assume we're talking about HP-UX 11
Yes, +DD64 is 11.X only.
: amanda I tried the hpux64-parisc2-cc with your patch applied to the
: amanda 0924 snapshot. It fails like so,
: amanda
: amanda some warnings early in the
Michael Ströder wrote:
Richard Levitte - VMS Whacker wrote:
X509_NAME_oneline(), it's displayed as "/Email=...". Other products,
like the JDK, seem to name it "/EmailAddress=...". As you can see,
that will create a problem when you try to use the representation used
by one system
On Mon, Sep 25, 2000, Anton J. Gamel wrote:
Who the hell removed the support for hpux 10 i.e.
NON-PARISC hardware with m68k??
Why the hell didn't you tell us during the beta period?
Actually, why the hell don'tyou send us a patch to config
to properly recognize your system??
___
Get your free e-mail, groups, calendar and more! http://www.bantu.com
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Peter Sylvester wrote:
For those who haven't see the following.
Thanks for the link. How can I subscribe to this list?
Ciao, Michael.
__
OpenSSL Project http://www.openssl.org
Development
From: Michael **UNKNOWN CHARSET** [EMAIL PROTECTED]
michael Richard Levitte - VMS Whacker wrote:
michael
michael But for example, the
michael "legal" shortnames for the DN attributes should be available
michael somewhere.
michael
michael Can you list a limited set of attribute types for
From: "Oscar Jacobsson" [EMAIL PROTECTED]
oscar.jacobsson 'commonName' and 'cn' are not long and short names
oscar.jacobsson for 2.5.4.3, rather ASN.1 and UTF-8 (string) names.
Hmm, that (and the rest of your explanation) made the whole thing a
bit more comprehensible. Thanks, buddy.
--
In this whole discussion about OIDs and object names, there's one
thought that I think Mickael Ströder mentioned about having the object
names completely configurable through a file or maybe a section of
openssl.cnf. On the other hand, as it is today, there are a number of
places in OpenSSL
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Richard Levitte - VMS
Whacker
Sent: den 25 september 2000 23:14
To: [EMAIL PROTECTED]
Subject: Objects and a configuration file
[...]
I'm definitely willing to redesign the contents of
A few thoughts:
1. I can see lots of value in using a file (that maps an object identifier's
numeric representation to and from its string representation) when decoding.
I can't see much use when encoding. Perhaps someone else can?
2. When possible, use an existing standard. RFC 2253's oid =
From: Frank Balluffi [EMAIL PROTECTED]
frankb 1. I can see lots of value in using a file (that maps an
frankb object identifier's numeric representation to and from its
frankb string representation) when decoding. I can't see much use
frankb when encoding. Perhaps someone else can?
Depends on
I'm definitely willing to redesign the contents of objects.txt
Perhaps it should be like /etc/hosts -- first the guaranteed unique part (the
OID),
then a list of names. The first is the official name -- what to use on
output. Any others are aliases -- what can be accepted on input. Unclear
target: hpux64-parisc-cc
compiler: $(what /usr/bin/cc)
LINT A.11.01.20 CXREF A.11.01.20
HP92453-01 A.11.01.20 HP C Compiler
$ CUPI80_IC7 Jan 7 1999 11:20:34 $
cc -o openssl -DMONOLITH -I../include -DTHREADS -D_REENTRANT -DDSO_DLFCN
-DHAVE_DLFCN_H -Ae +DD64 +O3
From: zhu qun-ying [EMAIL PROTECTED]
qyzhu Sorry, there is typo in my previous patch.
Actually, I'm surprised that fixed anything. The actual error is in
mkdef.pl, which isn't as selective as it should when it creates the
.def file...
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL
From: zhu qun-ying [EMAIL PROTECTED]
qyzhu I believe the error will happen when other alogo. are disable
qyzhu when they have a EVP_ entry in the evp.h. I try to add in the
qyzhu #ifndef ... for the the functions, but it seems have no effect
qyzhu on the generation process.
After you do that,
OpenSSL version 0.9.6 released
===
OpenSSL - The Open Source toolkit for SSL/TLS
http://www.openssl.org/
The OpenSSL project team is pleased to announce the release of version
0.9.6 of our open source toolkit for SSL/TLS. This new OpenSSL version
is a
44 matches
Mail list logo
