Geoff Hutchison on Tue 12/06 19:37 -0400:
> > There is a patch, I think it is ssl.3 or ssl.4, that you need to use
> > in order for SSL to work. Why this isn't in the standard
> > distribution, I have no idea.
>
> b) At the time 3.1.5 came out, it was unclear whether it was legal for
> free software to link to an SSL implementation in the US. Since the
> original author and myself happen to live in the US, that's a bit of a
> problem.
Well the patches were always available on the same US FTP sites if I
recall, and personally I think that if laws went so far as to say you
couldn't even hook into a separate library that you don't distribute and
didn't write, I think I would very much enjoy breaking such a
disturbing, ignorant law.
But anyways the crypto situation in the US is much improved as of, I
think some time in 1999 or 2000. You just have to put some dumb stuff
like this:
This site includes publicly available encryption source code
which, together with object code resulting from the compiling of
publicly available source code, may be exported from the United
States under License Exception "TSU" pursuant to 15 C.F.R. Section
740.13(e).
(see http://www.bxa.doc.gov/)
on your site (although that's a pretty pointless requirement if you ask
me; I sure wouldn't do it).
Sorry if this has already been discussed, I'm jumping in in the middle
it appears.
_______________________________________________
htdig-dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/htdig-dev
