Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-13 Thread Richard Levitte - VMS Whacker 
In message <[EMAIL PROTECTED]> on Mon, 13 Jan 2003 15:36:40 
+0100, Corinna Vinschen <[EMAIL PROTECTED]> said:

vinschen> in the meantime I released Cygwin's openssl using the above
vinschen> packaging scheme.  Would you mind to revert the cygwin.sh
vinschen> changes?  The following patch should do it:

Applied and committed.

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-13 Thread Corinna Vinschen 
On Fri, Jan 10, 2003 at 07:27:35PM +0100, Corinna Vinschen wrote:
> > [...]
> Hi, I have chosen another packaging method:
> 
>   Version 0.9.6h will consist only of the needed DLLs to link applications
>   build against it.
> 
>   The package will be called
> 
> openssl096-0.9.6h-1.tar.bz2
> 
>   The new 0.9.7 version will become the openssl package again, as the
>   0.9.6 version before.  So the new packages are still just called
>   "openssl":
> 
> openssl-0.9.7-1.tar.bz2
> openssl-devel-0.9.7-1.tar.bz2
> openssl-0.9.7-1-src.tar.bz2
> 
> That means, the patch to util/cygwin.sh can be reverted to create
> the normal openssh packages again instead of openssh2.
> 
> Is that ok with you?  Would you revert the cygwin.sh patch then?

Hi,

in the meantime I released Cygwin's openssl using the above packaging
scheme.  Would you mind to revert the cygwin.sh changes?  The following
patch should do it:

Index: util/cygwin.sh
===
RCS file: /home/cvs/cvsroot/src/openssl/util/cygwin.sh,v
retrieving revision 1.3
diff -u -p -r1.3 cygwin.sh
--- util/cygwin.sh  2003/01/09 16:15:46 1.3
+++ util/cygwin.sh  2003/01/13 14:35:19
@@ -114,13 +114,13 @@ strip usr/bin/*.exe usr/bin/*.dll
 # Runtime package
 find etc usr/bin usr/doc usr/ssl/certs usr/ssl/man/man[157] usr/ssl/misc \
  usr/ssl/openssl.cnf usr/ssl/private -empty -o \! -type d |
-tar cjfT openssl2-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl-${VERSION}-${SUBVERSION}.tar.bz2 -
 # Development package
 find usr/include usr/lib usr/ssl/man/man3 -empty -o \! -type d |
-tar cjfT openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
 
-ls -l openssl2-${VERSION}-${SUBVERSION}.tar.bz2
-ls -l openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2
 
 cleanup
 
Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-12 Thread Doug Kaufman 
On Sun, 12 Jan 2003, Andy Polyakov wrote:

> > > > I tried this patch on DJGPP both as normally compiled and also using
> > > > the asm modules (put ${x86_out_asm} in the DJGPP config-string
> > >   ^^^ Oh! I missed that. I mean the fact that they are not
> > > actually engaged in the default configuration. Any particular reason
> > > why?
> > 
> > The only reason is to maintain 386 compatibility. The last time I
> > asked (I think it was about a year ago), there was a question as to
> > whether 386 incompatible instructions were used in the asm files, even
> > if "386" was specified in the Configure options.
> 
> If you './Configure ... DJGPP 386', then pure 386 asm code will be
> generated. Well, it's all about single instruction, bswapl to be
> specific... A.

In that case, it probably makes sense to make the asm code the
default in DJGPP also. This should just take a change in the DJGPP
config-string in Configure to put ${x86_out_asm} into the (currently
blank) next field after ${x86_gcc_opts}.
Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-12 Thread Andy Polyakov 
> > > I tried this patch on DJGPP both as normally compiled and also using
> > > the asm modules (put ${x86_out_asm} in the DJGPP config-string
> >   ^^^ Oh! I missed that. I mean the fact that they are not
> > actually engaged in the default configuration. Any particular reason
> > why?
> 
> The only reason is to maintain 386 compatibility. The last time I
> asked (I think it was about a year ago), there was a question as to
> whether 386 incompatible instructions were used in the asm files, even
> if "386" was specified in the Configure options.

If you './Configure ... DJGPP 386', then pure 386 asm code will be
generated. Well, it's all about single instruction, bswapl to be
specific... A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-12 Thread Doug Kaufman 
On Sun, 12 Jan 2003, Andy Polyakov wrote:

> > I tried this patch on DJGPP both as normally compiled and also using
> > the asm modules (put ${x86_out_asm} in the DJGPP config-string
>   ^^^ Oh! I missed that. I mean the fact that they are not
> actually engaged in the default configuration. Any particular reason
> why?

The only reason is to maintain 386 compatibility. The last time I
asked (I think it was about a year ago), there was a question as to
whether 386 incompatible instructions were used in the asm files, even
if "386" was specified in the Configure options. DJGPP programs should
be able to work on the 386 architecture. I don't have a 386 machine
to test with. I have no objection to using the asm files as long as
doing so doesn't break 386 compatibility. If the 386 compatibility
problem is real, perhaps instructions for changing the config-string
in Configure should be put in INSTALL.DJGPP, for those wishing to use
the asm files. I am not a programmer and don't know how to check for
assembler instructions incompatible with the 386 myself.
 Doug
-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-12 Thread Andy Polyakov 
> > This is a preliminary patch and I need to think it through before I
> > commit it. Maybe we should solve it in some other way (like with ELF).
> > Any DJGPP out there who care to verify if this doesn't break DJGPP?
> 
> I tried this patch on DJGPP both as normally compiled and also using
> the asm modules (put ${x86_out_asm} in the DJGPP config-string
  ^^^ Oh! I missed that. I mean the fact that they are not
actually engaged in the default configuration. Any particular reason
why?

> No problems with compilation or testing.

Great! As for "preliminarity" of the patch. I've chosen to just promote
it to "final" and throw it in and not do something similar to ELF
solution. Basically because of lack of motivation:-) Cheers. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-11 Thread Doug Kaufman 
On Thu, 9 Jan 2003, Andy Polyakov wrote:

> I found the documentation for .def ... .endef, but it doesn't say a
> thing about the values of .scl and .type. So I just copied from an .s
> file generated by compiler. Verify the values with your people.
> 
> This is a preliminary patch and I need to think it through before I
> commit it. Maybe we should solve it in some other way (like with ELF).
> Any DJGPP out there who care to verify if this doesn't break DJGPP?
> 
> Oh! BTW, I probably have to object against calling the package openssl2,
> openssl097 is probably more appropriate. A.
> 
> *** crypto/perlasm/x86asm.pl.orig   Thu Jul 18 14:38:03 2002
> --- crypto/perlasm/x86asm.plThu Jan  9 20:41:52 2003

I tried this patch on DJGPP both as normally compiled and also using
the asm modules (put ${x86_out_asm} in the DJGPP config-string in
Configure). No problems with compilation or testing.
Doug

-- 
Doug Kaufman
Internet: [EMAIL PROTECTED]

__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-10 Thread Corinna Vinschen 
On Thu, Jan 09, 2003 at 10:35:16PM +0100, Corinna Vinschen wrote:
> The "2" is just sort of a counter which is needed to allow more than
> [...]

Hi, I have chosen another packaging method:

  Version 0.9.6h will consist only of the needed DLLs to link applications
  build against it.

  The package will be called

openssl096-0.9.6h-1.tar.bz2

  The new 0.9.7 version will become the openssl package again, as the
  0.9.6 version before.  So the new packages are still just called
  "openssl":

openssl-0.9.7-1.tar.bz2
openssl-devel-0.9.7-1.tar.bz2
openssl-0.9.7-1-src.tar.bz2

That means, the patch to util/cygwin.sh can be reverted to create
the normal openssh packages again instead of openssh2.

Is that ok with you?  Would you revert the cygwin.sh patch then?

Thanks in advance,
Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Corinna Vinschen 
On Thu, Jan 09, 2003 at 08:58:29PM +0100, Andy Polyakov wrote:
> I found the documentation for .def ... .endef, but it doesn't say a
> thing about the values of .scl and .type. So I just copied from an .s
> file generated by compiler. Verify the values with your people.

This is from the gas info pages:

--- SNIP ---

`.scl CLASS'


   Set the storage-class value for a symbol.  This directive may only be
used inside a `.def'/`.endef' pair.  Storage class may flag whether a
symbol is static or external, or it may record further symbolic
debugging information.

   The `.scl' directive is primarily associated with COFF output; when
configured to generate `b.out' output format, `as' accepts this
directive but ignores it.

`.type INT' (COFF version)
==

   This directive, permitted only within `.def'/`.endef' pairs, records
the integer INT as the type attribute of a symbol table entry.

   `.type' is associated only with COFF format output; when `as' is
configured for `b.out' output, it accepts this directive but ignores it.

--- SNAP ---

The value needed for .scl is C_EXT = 2
and the value for .type is (DT_FCN << N_BTSHFT) = 32

so that should be ok.

> Oh! BTW, I probably have to object against calling the package openssl2,
> openssl097 is probably more appropriate. A.

The "2" is just sort of a counter which is needed to allow more than
one package installed at the same time.  E.g. we have two concurrent
versions of libreadline called libreadline4 and libreadline5.  This
is *not* related to the official version number of the packages, which
in case of the libreadline packages are 4.1 and 4.3.  This official
version number is part of the full package name, e.g. in case of
libreadline currently:

libreadline4-4.1-2.tar.bz2
libreadline5-4.3-2.tar.bz2
 
so in case of openssl this will become

openssl-0.9.6h-2.tar.bz2
openssl2-0.9.7-1.tar.bz2

The next version, 0.9.8, would become

openssl3-0.9.8-1.tar.bz2

The names of the real DLLs don't contain this counter:

  cygcrypto.dll   == 0.9.6x, no version number for backward compatibility
  cygcrypto.dll-0.9.7
  cygcrypto.dll-0.9.8

> *** crypto/perlasm/x86asm.pl.orig   Thu Jul 18 14:38:03 2002
> --- crypto/perlasm/x86asm.plThu Jan  9 20:41:52 2003
> ***
> *** 91,97 
>   #undef SIZE
>   #undef TYPE
>   #define SIZE(a,b)
> ! #define TYPE(a,b)
>   #endif /* __CYGWIN || __DJGPP */
>   #endif
> 
> --- 91,97 
>   #undef SIZE
>   #undef TYPE
>   #define SIZE(a,b)
> ! #define TYPE(a,b) .def a; .scl 2; .type 32; .endef
>   #endif /* __CYGWIN || __DJGPP */
>   #endif

Builds fine, all tests pass, ssh works again with this patch.

Thanks very much!
Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Andy Polyakov 
> > And I don't think it's openssl's fault.
> 
> Yes, it apparently is...

Verify that the attached patch solves the problem.

> > I'm going
> > to ask some linker experts...
> 
> Ask about this .def ... .endef line. Any documentation available
> on-line?

I found the documentation for .def ... .endef, but it doesn't say a
thing about the values of .scl and .type. So I just copied from an .s
file generated by compiler. Verify the values with your people.

This is a preliminary patch and I need to think it through before I
commit it. Maybe we should solve it in some other way (like with ELF).
Any DJGPP out there who care to verify if this doesn't break DJGPP?

Oh! BTW, I probably have to object against calling the package openssl2,
openssl097 is probably more appropriate. A.

*** crypto/perlasm/x86asm.pl.orig   Thu Jul 18 14:38:03 2002
--- crypto/perlasm/x86asm.plThu Jan  9 20:41:52 2003
***
*** 91,97 
  #undef SIZE
  #undef TYPE
  #define SIZE(a,b)
! #define TYPE(a,b)
  #endif /* __CYGWIN || __DJGPP */
  #endif

--- 91,97 
  #undef SIZE
  #undef TYPE
  #define SIZE(a,b)
! #define TYPE(a,b) .def a; .scl 2; .type 32; .endef
  #endif /* __CYGWIN || __DJGPP */
  #endif
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Andy Polyakov 
> And I don't think it's openssl's fault.

Yes, it apparently is... Compile foo(){} with cc -S and note that
compiler add some .def ... .endef line, but not perlasm thing which is
reponsible for assembler code generation.

> I'm going
> to ask some linker experts...

Ask about this .def ... .endef line. Any documentation available
on-line?

> > Did it ever work? Assembler support in cygwin-shared build that is? BN
> 
> I can't tell.  I never saw that problem before and in 0.9.6h all tests
> pass.

0.9.6h doesn't provide assembler support for Cygwin. A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Corinna Vinschen 
On Thu, Jan 09, 2003 at 06:32:05PM +0100, Andy Polyakov wrote:
> > > > > Until I found a solution for that linker problem (which is a linker bug,
> > > > > apparently) I'd like to build the Cygwin version using rc4_enc.o.  How
> > > > > can I do that most cleanly?
> > > >
> > > > By fixing rx86-out.o:-) A.
> 
> Did it ever work? Assembler support in cygwin-shared build that is? BN

I can't tell.  I never saw that problem before and in 0.9.6h all tests
pass.

Sorry,
Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Corinna Vinschen 
On Thu, Jan 09, 2003 at 06:25:57PM +0100, Andy Polyakov wrote:
> I meant "be patient:-)" As for details, you should have provided more of
> them:-) At least that you've configured with shared flag and that 'make
> test' fails. In other words something we can *easily* reproduce. Cheers.

Uhm... I thought that was clear from the context.  I was talking about
building DLLs already in my first posting and my fix to Makefile.org
was related to that.  And I don't think it's openssl's fault.  It's
very likely a linker problem when generating the DLL and link stub from
the static lib (which is working fine even with the assembler code).
I just wasn't able to find out why the linker fails so far.  I'm going
to ask some linker experts...

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Andy Polyakov 
> > > > > Until I found a solution for that linker problem (which is a linker bug,
> > > > > apparently) I'd like to build the Cygwin version using rc4_enc.o.  How
> > > > > can I do that most cleanly?
> > > >
> > > > By fixing rx86-out.o:-) A.
> 
> Did it ever work? Assembler support in cygwin-shared build that is? BN
> stuff works, but I bet that's because routines from crypto/bn/asm/*.o
> are never called from application, but internally from within
> libcrypto.dll... A.

OK, I've got test/rc4test.exe working, but I have to leave now... A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Andy Polyakov 
> > > > Until I found a solution for that linker problem (which is a linker bug,
> > > > apparently) I'd like to build the Cygwin version using rc4_enc.o.  How
> > > > can I do that most cleanly?
> > >
> > > By fixing rx86-out.o:-) A.

Did it ever work? Assembler support in cygwin-shared build that is? BN
stuff works, but I bet that's because routines from crypto/bn/asm/*.o
are never called from application, but internally from within
libcrypto.dll... A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Andy Polyakov 
> > As for .*_end symbols. Apparently there're more... Any particular reason
> > why are you complaining just about .RC4_end?
> 
> No.  Just the one I found first due to the ssh crash.
> 
> > > Until I found a solution for that linker problem (which is a linker bug,
> > > apparently) I'd like to build the Cygwin version using rc4_enc.o.  How
> > > can I do that most cleanly?
> >
> > By fixing rx86-out.o:-) A.
> 
> That doesn't help w/o details.

I meant "be patient:-)" As for details, you should have provided more of
them:-) At least that you've configured with shared flag and that 'make
test' fails. In other words something we can *easily* reproduce. Cheers.
A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Corinna Vinschen 
On Thu, Jan 09, 2003 at 05:53:57PM +0100, Andy Polyakov wrote:
> As for .*_end symbols. Apparently there're more... Any particular reason
> why are you complaining just about .RC4_end?

No.  Just the one I found first due to the ssh crash.

> > Until I found a solution for that linker problem (which is a linker bug,
> > apparently) I'd like to build the Cygwin version using rc4_enc.o.  How
> > can I do that most cleanly?
> 
> By fixing rx86-out.o:-) A.

That doesn't help w/o details.  I don't see anything wrong with that
file.  I have no idea why our linker treats RC4 from that file (and
other functions from assembler files, apparently) as data.

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Richard Levitte - VMS Whacker 
In message <[EMAIL PROTECTED]> on Thu, 9 Jan 2003 17:26:12 
+0100, Corinna Vinschen <[EMAIL PROTECTED]> said:

vinschen> What I don't understand is the following.
vinschen> 
vinschen> crypto/rc4/Makefile.ssl contains the following:
vinschen> 
vinschen>   RC4_ENC=rc4_enc.o
vinschen>   # or use
vinschen>   #RC4_ENC=asm/rx86-elf.o
vinschen>   #RC4_ENC=asm/rx86-out.o
vinschen>   #RC4_ENC=asm/rx86-sol.o
vinschen>   #RC4_ENC=asm/rx86bdsi.o
vinschen> 
vinschen> Even though it's supposed to build rc4_enc.o to get the RC4
vinschen> function(s), it builds asm/rx86-out.o instead.

What's given in crypto/rc4/Makefile.ssl is immaterial, since the
correct values are passed on the command line by parent makes (see
Makefile.ssl and crypto/Makefile.ssl).

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Richard Levitte - VMS Whacker 
In message <[EMAIL PROTECTED]> on Thu, 09 Jan 2003 17:34:39 +0100, Andy 
Polyakov <[EMAIL PROTECTED]> said:

appro> > c=`echo $$i | sed 's/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`;
appro>  ^ this of course works, but it probably
appro> should be \., not just dot:-)

I saw it and fixed it before committing.

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Andy Polyakov 
>  What I don't understand is the following.
> 
> crypto/rc4/Makefile.ssl contains the following:
> 
>   RC4_ENC=rc4_enc.o
>   # or use
>   #RC4_ENC=asm/rx86-elf.o
>   #RC4_ENC=asm/rx86-out.o
>   #RC4_ENC=asm/rx86-sol.o
>   #RC4_ENC=asm/rx86bdsi.o
> 
> Even though it's supposed to build rc4_enc.o to get the RC4 function(s),
> it builds asm/rx86-out.o instead.

RC4_ENC gets overriden from top Makefile.

As for .*_end symbols. Apparently there're more... Any particular reason
why are you complaining just about .RC4_end?

> Until I found a solution for that linker problem (which is a linker bug,
> apparently) I'd like to build the Cygwin version using rc4_enc.o.  How
> can I do that most cleanly?

By fixing rx86-out.o:-) A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Corinna Vinschen 
On Thu, Jan 09, 2003 at 05:34:39PM +0100, Andy Polyakov wrote:
> > Btw., does anybody have an idea where a symbol ".RC4_end" could come from?
> 
> I should have an idea... To start which I didn't expect to see .RC4_end
> symbol be visible at all. Assembler should have hidden it as names
> starting with . are supposed to be internal. I can double-check it later
> today. As for dropped RC4 symbol. I'm not really following... Did 'make
> test' pass?

No.  The problem is that when creating the link stub, the _RC4 symbol
is treated as a data or bss symbol, not a text symbol.  Linking against
that link stub creates an illegal reference into the DLL ==> rc4test
crashes.

The same happens with _DES_ede3_cbc_encrypt and _DES_ncbc_encrypt, resulting
in destest crashing.

This all doesn't happen when linking against the static crypto lib, btw.,
it's justy a problem of the dynamic linking process.

> > c=`echo $$i | sed 's/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`;
>  ^ this of course works, but it probably
> should be \., not just dot:-)

Oops, you're right.

Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Andy Polyakov 
> However, currently I'm unfortunately unable to release a Cygwin net
> version of 0.9.7 due to a linker problem, which results in dropped
> symbols in the link stub library.  The most prominent dropped symbol
> is RC4.  Building OpenSSH with this libs results in ssh and sshd crashing
> immediately :-(((  I'm still in the process of trying to find out why
> that happens.
> 
> Btw., does anybody have an idea where a symbol ".RC4_end" could come from?

I should have an idea... To start which I didn't expect to see .RC4_end
symbol be visible at all. Assembler should have hidden it as names
starting with . are supposed to be internal. I can double-check it later
today. As for dropped RC4 symbol. I'm not really following... Did 'make
test' pass?

> c=`echo $$i | sed 's/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`;
 ^ this of course works, but it probably
should be \., not just dot:-)

A.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Corinna Vinschen 
On Thu, Jan 09, 2003 at 05:10:55PM +0100, Richard Levitte - VMS Whacker wrote:
> In message <[EMAIL PROTECTED]> on Thu, 9 Jan 2003 17:05:12 
>+0100, Corinna Vinschen <[EMAIL PROTECTED]> said:
> 
> vinschen> Btw., does anybody have an idea where a symbol ".RC4_end" could come from?
> 
> crypto/rc4/asm/rx86unix.cpp in my case (on Linux)...
> 
> I've applied your patches, and will commit them promptly.  Please
> check the next snapshot.

Thanks, I just found out that the symbol comes from rx86unix.cpp in my
case, too.  What I don't understand is the following.

crypto/rc4/Makefile.ssl contains the following:

  RC4_ENC=rc4_enc.o
  # or use
  #RC4_ENC=asm/rx86-elf.o
  #RC4_ENC=asm/rx86-out.o
  #RC4_ENC=asm/rx86-sol.o
  #RC4_ENC=asm/rx86bdsi.o

Even though it's supposed to build rc4_enc.o to get the RC4 function(s),
it builds asm/rx86-out.o instead.

However, I found out, that the linker problem disappears if I build
the libraries using rc4_enc.o instead of asm/rx86-out.o.  Frankly,
I have NO idea why!

Until I found a solution for that linker problem (which is a linker bug,
apparently) I'd like to build the Cygwin version using rc4_enc.o.  How
can I do that most cleanly?

Thanks in advance,
Corinna

-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Richard Levitte - VMS Whacker 
In message <[EMAIL PROTECTED]> on Thu, 9 Jan 2003 17:05:12 
+0100, Corinna Vinschen <[EMAIL PROTECTED]> said:

vinschen> Btw., does anybody have an idea where a symbol ".RC4_end" could come from?

crypto/rc4/asm/rx86unix.cpp in my case (on Linux)...

I've applied your patches, and will commit them promptly.  Please
check the next snapshot.

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-168 35  BROMMA  \ T: +46-8-26 52 47
\  SWEDEN   \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis-- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See  for more info.
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2003-01-09 Thread Corinna Vinschen 
On Tue, Dec 31, 2002 at 01:34:07AM +0100, Richard Levitte - VMS Whacker wrote:
> -BEGIN PGP SIGNED MESSAGE-
> 
> 
>   OpenSSL version 0.9.7 released
>   ===

Hi,

sorry for the late response but I didn't manage to test earlier :-(

I have two patches attached which are necessary to build 0.9.7 for
the Cygwin release.  The Makefile.org patch is necessary to build
the Cygwin DLLs at all.  It fixes a wrong sed expression.  The patch
to util/cygwin.sh is required by the naming scheme used in the Cygwin
net release.

However, currently I'm unfortunately unable to release a Cygwin net
version of 0.9.7 due to a linker problem, which results in dropped
symbols in the link stub library.  The most prominent dropped symbol
is RC4.  Building OpenSSH with this libs results in ssh and sshd crashing
immediately :-(((  I'm still in the process of trying to find out why
that happens.

Btw., does anybody have an idea where a symbol ".RC4_end" could come from?

Corinna


--- openssl-0.9.7.orig/Makefile.org 2002-12-30 00:03:16.0 +0100
+++ openssl-0.9.7/Makefile.org  2003-01-07 19:25:50.0 +0100
@@ -749,7 +749,7 @@ install: all install_docs
chmod 555 
$(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new; \
mv -f 
$(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i.new $(INSTALL_PREFIX)$(INSTALLTOP)/lib/$$i; \
else \
-   c=`echo $$i | sed 
's/^lib\(.*\)/cyg\1-$(SHLIB_VERSION_NUMBER)/'`; \
+   c=`echo $$i | sed 
+'s/^lib\(.*\).dll/cyg\1-$(SHLIB_VERSION_NUMBER).dll/'`; \
cp $$c 
$(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new; \
chmod 755 
$(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new; \
mv -f 
$(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c.new $(INSTALL_PREFIX)$(INSTALLTOP)/bin/$$c; \
--- openssl-0.9.7.orig/util/cygwin.sh   2002-11-14 13:39:51.0 +0100
+++ openssl-0.9.7/util/cygwin.sh2003-01-07 19:25:15.0 +0100
@@ -114,13 +114,13 @@ strip usr/bin/*.exe usr/bin/*.dll
 # Runtime package
 find etc usr/bin usr/doc usr/ssl/certs usr/ssl/man/man[157] usr/ssl/misc \
  usr/ssl/openssl.cnf usr/ssl/private -empty -o \! -type d |
-tar cjfT openssl-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl2-${VERSION}-${SUBVERSION}.tar.bz2 -
 # Development package
 find usr/include usr/lib usr/ssl/man/man3 -empty -o \! -type d |
-tar cjfT openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
+tar cjfT openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2 -
 
-ls -l openssl-${VERSION}-${SUBVERSION}.tar.bz2
-ls -l openssl-devel-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl2-${VERSION}-${SUBVERSION}.tar.bz2
+ls -l openssl2-devel-${VERSION}-${SUBVERSION}.tar.bz2
 
 cleanup
 


-- 
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:[EMAIL PROTECTED]
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2002-12-30 Thread Kris Kennaway 
On Mon, Dec 30, 2002 at 10:45:30PM -0800, Kris Kennaway wrote:
> On Tue, Dec 31, 2002 at 01:34:07AM +0100, Richard Levitte - VMS Whacker wrote:
> 
> >   o Support for new platforms: Windows CE, Tandem OSS, A/UX, AIX 64-bit,
> > Linux x86_64, Linux 64-bit on Sparc v9
> 
> OpenSSL does not compile out of the box on FreeBSD/SPARC (see
> attached) - it tries to use the x86 FreeBSD-elf target.  The
> linux/sparc configuration is probably a base for fixing this.
> 
> Kris

This patch appears to fix it (I stole the OpenBSD-sparc64 config
target).  OpenSSL builds and passes 'make test'.

Kris

--- config.orig Fri Dec  6 08:45:11 2002
+++ config  Mon Dec 30 23:24:03 2002
@@ -206,6 +206,7 @@
Pentium\ II*) MACH="i686" ;;
Pentium*) MACH="i586" ;;
Alpha*  ) MACH="alpha";;
+  *Sparc* ) MACH="sparc64"  ;;
*   ) MACH="$MACHINE" ;;
 esac
 case ${MACH} in
@@ -640,6 +641,7 @@
   *86*-*-solaris2) OUT="solaris-x86-$CC" ;;
   *-*-sunos4) OUT="sunos-$CC" ;;
   alpha*-*-freebsd*) OUT="FreeBSD-alpha" ;;
+  sparc64-*-freebsd*) OUT="FreeBSD-sparc64" ;;
   *-freebsd[3-9]*) OUT="FreeBSD-elf" ;;
   *-freebsd[1-2]*) OUT="FreeBSD" ;;
   *86*-*-netbsd) OUT="NetBSD-x86" ;;
--- Configure.orig  Fri Dec 27 17:35:11 2002
+++ Configure   Mon Dec 30 23:24:03 2002
@@ -396,6 +396,7 @@
 "NetBSD-m68",  "gcc:-DTERMIOS -O3 -fomit-frame-pointer -Wall 
-DB_ENDIAN::(unknown):::BN_LLONG MD2_CHAR RC4_INDEX 
DES_UNROLL::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
 "NetBSD-x86",  "gcc:-DTERMIOS -O3 -fomit-frame-pointer -m486 
-Wall::(unknown):::BN_LLONG ${x86_gcc_des} 
${x86_gcc_opts}::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
 "FreeBSD-elf",  "gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486 
-Wall::-pthread -D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE:::BN_LLONG ${x86_gcc_des} 
${x86_gcc_opts}:${x86_elf_asm}:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
+"FreeBSD-sparc64","gcc:-DB_ENDIAN -DTERMIOS -O3 
+-fomit-frame-pointer::(unknown):::SIXTY_FOUR_BIT_LONG DES_INT DES_PTR DES_RISC2 
+BF_PTR::dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",
 "FreeBSD",  "gcc:-DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3 -m486 
-Wall::(unknown):::BN_LLONG ${x86_gcc_des} ${x86_gcc_opts}:${x86_out_asm}",
 "bsdi-gcc", "gcc:-O3 -ffast-math -DL_ENDIAN -DPERL5 -m486::(unknown):::RSA_LLONG 
${x86_gcc_des} ${x86_gcc_opts}:${x86_bsdi_asm}",
 "bsdi-elf-gcc", "gcc:-DPERL5 -DL_ENDIAN -fomit-frame-pointer -O3 -m486 
-Wall::(unknown)::-ldl:BN_LLONG ${x86_gcc_des} 
${x86_gcc_opts}:${x86_elf_asm}:dlfcn:bsd-gcc-shared:-fPIC::.so.\$(SHLIB_MAJOR).\$(SHLIB_MINOR)",



msg14674/pgp0.pgp
Description: PGP signature

Re: [ANNOUNCE] OpenSSL 0.9.7 released

2002-12-30 Thread Kris Kennaway 
On Tue, Dec 31, 2002 at 01:34:07AM +0100, Richard Levitte - VMS Whacker wrote:

>   o Support for new platforms: Windows CE, Tandem OSS, A/UX, AIX 64-bit,
> Linux x86_64, Linux 64-bit on Sparc v9

OpenSSL does not compile out of the box on FreeBSD/SPARC (see
attached) - it tries to use the x86 FreeBSD-elf target.  The
linux/sparc configuration is probably a base for fixing this.

Kris

Script started on Mon Dec 30 22:42:00 2002
You have mail.
enigma# ./config

Operating system: sparc64-whatever-freebsd5.0
Configuring for FreeBSD-elf
Configuring for FreeBSD-elf
IsWindows=0
CC=gcc
CFLAG =-DOPENSSL_THREADS -pthread -D_REENTRANT -D_THREAD_SAFE -D_THREADSAFE 
-DDSO_DLFCN -DHAVE_DLFCN_H -DOPENSSL_NO_KRB5 -DTERMIOS -DL_ENDIAN -fomit-frame-pointer 
-O3 -m486 -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM
EX_LIBS   =
BN_ASM=asm/bn86-elf.o asm/co86-elf.o
DES_ENC   =asm/dx86-elf.o asm/yx86-elf.o
BF_ENC=asm/bx86-elf.o
CAST_ENC  =asm/cx86-elf.o
RC4_ENC   =asm/rx86-elf.o
RC5_ENC   =asm/r586-elf.o
MD5_OBJ_ASM   =asm/mx86-elf.o
SHA1_OBJ_ASM  =asm/sx86-elf.o
RMD160_OBJ_ASM=asm/rm86-elf.o
PROCESSOR =
RANLIB=/usr/bin/ranlib
ARFLAGS   =
PERL  =/usr/bin/perl5
THIRTY_TWO_BIT mode
DES_PTR used
DES_RISC1 used
DES_UNROLL used
BN_LLONG mode
RC4_INDEX mode
RC4_CHUNK is undefined
Makefile => Makefile.ssl
e_os2.h => include/openssl/e_os2.h [File exists]
making links in crypto...
Makefile => Makefile.ssl
crypto.h => ../include/openssl/crypto.h [File exists]
tmdiff.h => ../include/openssl/tmdiff.h [File exists]
opensslv.h => ../include/openssl/opensslv.h [File exists]
opensslconf.h => ../include/openssl/opensslconf.h [File exists]
ebcdic.h => ../include/openssl/ebcdic.h [File exists]
symhacks.h => ../include/openssl/symhacks.h [File exists]
ossl_typ.h => ../include/openssl/ossl_typ.h [File exists]
Makefile => Makefile.ssl
making links in crypto/md2...
Makefile => Makefile.ssl
md2.h => ../../include/openssl/md2.h [File exists]
md2test.c => ../../test/md2test.c [File exists]
making links in crypto/md4...
Makefile => Makefile.ssl
md4.h => ../../include/openssl/md4.h [File exists]
md4test.c => ../../test/md4test.c [File exists]
md4.c => ../../apps/md4.c [File exists]
making links in crypto/md5...
Makefile => Makefile.ssl
md5.h => ../../include/openssl/md5.h [File exists]
md5test.c => ../../test/md5test.c [File exists]
making links in crypto/sha...
Makefile => Makefile.ssl
sha.h => ../../include/openssl/sha.h [File exists]
shatest.c => ../../test/shatest.c [File exists]
sha1test.c => ../../test/sha1test.c [File exists]
making links in crypto/mdc2...
Makefile => Makefile.ssl
mdc2.h => ../../include/openssl/mdc2.h [File exists]
mdc2test.c => ../../test/mdc2test.c [File exists]
making links in crypto/hmac...
Makefile => Makefile.ssl
hmac.h => ../../include/openssl/hmac.h [File exists]
hmactest.c => ../../test/hmactest.c [File exists]
making links in crypto/ripemd...
Makefile => Makefile.ssl
ripemd.h => ../../include/openssl/ripemd.h [File exists]
rmdtest.c => ../../test/rmdtest.c [File exists]
making links in crypto/des...
Makefile => Makefile.ssl
des.h => ../../include/openssl/des.h [File exists]
des_old.h => ../../include/openssl/des_old.h [File exists]
destest.c => ../../test/destest.c [File exists]
making links in crypto/rc2...
Makefile => Makefile.ssl
rc2.h => ../../include/openssl/rc2.h [File exists]
rc2test.c => ../../test/rc2test.c [File exists]
making links in crypto/rc4...
Makefile => Makefile.ssl
rc4.h => ../../include/openssl/rc4.h [File exists]
rc4test.c => ../../test/rc4test.c [File exists]
making links in crypto/rc5...
Makefile => Makefile.ssl
rc5.h => ../../include/openssl/rc5.h [File exists]
rc5test.c => ../../test/rc5test.c [File exists]
making links in crypto/idea...
Makefile => Makefile.ssl
idea.h => ../../include/openssl/idea.h [File exists]
ideatest.c => ../../test/ideatest.c [File exists]
making links in crypto/bf...
Makefile => Makefile.ssl
blowfish.h => ../../include/openssl/blowfish.h [File exists]
bftest.c => ../../test/bftest.c [File exists]
making links in crypto/cast...
Makefile => Makefile.ssl
cast.h => ../../include/openssl/cast.h [File exists]
casttest.c => ../../test/casttest.c [File exists]
making links in crypto/bn...
Makefile => Makefile.ssl
bn.h => ../../include/openssl/bn.h [File exists]
bntest.c => ../../test/bntest.c [File exists]
exptest.c => ../../test/exptest.c [File exists]
making links in crypto/ec...
Makefile => Makefile.ssl
ec.h => ../../include/openssl/ec.h [File exists]
ectest.c => ../../test/ectest.c [File exists]
making links in crypto/rsa...
Makefile => Makefile.ssl
rsa.h => ../../include/openssl/rsa.h [File exists]
rsa_test.c => ../../test/rsa_test.c [File exists]
making links in crypto/dsa...
Makefile => Makefile.ssl
dsa.h => ../../include/openssl/dsa.h [File exists]
dsatest.c => ../../test/ds

[ANNOUNCE] OpenSSL 0.9.7 released

2002-12-30 Thread Richard Levitte - VMS Whacker 
-BEGIN PGP SIGNED MESSAGE-


  OpenSSL version 0.9.7 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.7 of our open source toolkit for SSL/TLS.  This new
  OpenSSL version is a major release and incorporates at least 262
  changes and bugfixes to the toolkit (for a complete list see
  http://www.openssl.org/source/exp/CHANGES.

  The most significant changes are:

  o New library section OCSP.
  o Complete rewrite of ASN1 code.
  o CRL checking in verify code and openssl utility.
  o Extension copying in 'ca' utility.
  o Flexible display options in 'ca' utility.
  o Provisional support for international characters with UTF8.
  o Support for external crypto devices ('engine') is no longer
a separate distribution.
  o New elliptic curve library section.
  o New AES (Rijndael) library section.
  o Support for new platforms: Windows CE, Tandem OSS, A/UX, AIX 64-bit,
Linux x86_64, Linux 64-bit on Sparc v9
  o Extended support for some platforms: VxWorks
  o Enhanced support for shared libraries.
  o Now only builds PIC code when shared library support is requested.
  o Support for pkg-config.
  o Lots of new manuals.
  o Makes symbolic links to or copies of manuals to cover all described
functions.
  o Change DES API to clean up the namespace (some applications link also
against libdes providing similar functions having the same name).
Provide macros for backward compatibility (will be removed in the
future).
  o Unify handling of cryptographic algorithms (software and engine)
to be available via EVP routines for asymmetric and symmetric ciphers.
  o NCONF: new configuration handling routines.
  o Change API to use more 'const' modifiers to improve error checking
and help optimizers.
  o Finally remove references to RSAref.
  o Reworked parts of the BIGNUM code.
  o Support for new engines: Broadcom ubsec, Accelerated Encryption
Processing, IBM 4758.
  o A few new engines added in the demos area.
  o Extended and corrected OID (object identifier) table.
  o PRNG: query at more locations for a random device, automatic query for
EGD style random sources at several locations.
  o SSL/TLS: allow optional cipher choice according to server's preference.
  o SSL/TLS: allow server to explicitly set new session ids.
  o SSL/TLS: support Kerberos cipher suites (RFC2712).
Only supports MIT Kerberos for now.
  o SSL/TLS: allow more precise control of renegotiations and sessions.
  o SSL/TLS: add callback to retrieve SSL/TLS messages.
  o SSL/TLS: support AES cipher suites (RFC3268).

  We consider OpenSSL 0.9.7 to be the best version of OpenSSL available
  and we strongly recommend that users of older versions upgrade as
  soon as possible.  OpenSSL 0.9.7 is available for download via HTTP
  and FTP from the following master locations (you can find the various
  FTP mirrors under http://www.openssl.org/source/mirror.html):

o http://www.openssl.org/source/
o ftp://ftp.openssl.org/source/

  OpenSSL 0.9.6 (all patch levels) came in the form of two distributions,
  a "normal" one and an "engine" variant that included support for external
  crypto devices.  In 0.9.7, the "engine" framework is part of the "normal"
  distribution, so there are no variants of 0.9.7.

  The distribution file name is:

  o openssl-0.9.7.tar.gz [normal]
MD5 checksum: ef376d14205afcfb831cd3720f705d79

  The checksum was calculated using the following command:

openssl md5 < openssl-0.9.7.tar.gz

  Yours,
  The OpenSSL Project Team...  

Mark J. Cox Ben Laurie  Andy Polyakov
Ralf S. Engelschall Richard Levitte Geoff Thorpe
Dr. Stephen Henson  Bodo Möller
Lutz JänickeUlf Möller

-BEGIN PGP SIGNATURE-
Version: 2.6.3ia
Charset: noconv

iQEVAwUBPhDlY/Ty7ZjgbSyxAQEFlAgAktqLFxipUJnd64x/jShkBmgz+0hhhlfM
6bwMmNYYL8kMgsgvTdoqDgVD8gW3DoIv4xXKsamle9KCZY1aA6KFiU8NQMIzmr6U
e5FUvwkoaw+X2buF7B5oCGLFOrvgrvNiVjGRzOSp0l+CLXC0/DP9tuzJ/0RJZeko
YqDQVGAu+FhkZ5veIYTbo1vyuL4Vp6ZG+QMsHcEKfItV2rzCB9EPng7qQIU781a7
6kmLgMzNPsqWNW3Z6Ie6YpzVWVUxkiRBPCEEXlvc+jNdEbvG76ax8+Wje6PEsy78
KtRLbe9BAbBY0sMYB+0HEOZVeSZgqvLwhYm0aRg0VG/x3mTsSgSzxw==
=NTIE
-END PGP SIGNATURE-
__
OpenSSL Project http://www.openssl.org
Development Mailing List   [EMAIL PROTECTED]
Automated List Manager   [EMAIL PROTECTED]