In article <[EMAIL PROTECTED]> you wrote:
> I've haven't been able to perform a successful rsync for several
> days. Has anyone else had problems? Each attempt produces the same
> error, which looks like it is on the server side:
>>> rsync -rztpv --delete rsync://dev.openssl.org/openssl-cvs
>
I seem to remember we added that to the configure script just before
OpenSSL was born...
Ben Laurie wrote:
>
> Ben Laurie wrote:
> >
> > making all in err...
> > gcc -I.. -I../../include -DTERMIOS -DL_ENDIAN -fomit-frame-pointer -O3
> > -m486 -Wall -DSHA1_ASM -DMD5_ASM -DRMD160_ASM -c err_all.c
> No. Its my contention that if a US person exports crypto code >illegally,
>the US government will go after a US-related firm (i.e. a >multinational)
>who uses that code internationally. This is based on statements from
>government officials and discussions with export control attorneys.
M
I am currently working through putting together a glibc2 (2.0.6) linux (2.0.36)
system using the egcs-1.1.1 compiler - the other service of note on this system
is a NIS installation.
I hadn't meant to be into the OpenSSL intricacies this early in the
proceedings, but I wanted the DES routines
OK, you have a good point. Let me try again. A US-related firm
will not use illegally exported cryptography code for fear of stock
market and government retribution. I have direct experience with large
US-related firms for whom this has been an issue.
> > No. Its my contention that if
I'm forwarding it to the -dev list...
Jeremy Hylton wrote:
>
> I wanted to send a minor bug report, and used the address mentioned at
> the bottom of README.PROBLEMS -- [EMAIL PROTECTED] It
> bounced; either the address or the README.PROBLEMS ought to get fixed.
>
> (Would you like me to resen
Hi
I downloaded the current CVS tree (via rsync) and configured and built it
without problem. Then the 'make rehash' failed with the following message:
"c_rehash: rehashing skipped ('openssl' program still not available)"
This happens because in the Makefile.ssl the OPENSSL envvar is not set for
> A US-related firm
>will not use illegally exported cryptography code for fear of stock
>market and government retribution.
Okay, that makes sense to me.
__
OpenSSL Project http://www.open
It looks like the line
LIBSRC=md2_dgst.c md5_one.c
should read
LIBSRC=md2_dgst.c md2_one.c
--
;; Hugh Taylor [EMAIL PROTECTED]
;; Software Development
;; WRQ - Makers of Reflection and Express Software
;; Seattle, WA, USA
_
