Re: Optional cryptography
On Sat, 29 May 1999, Josip Rodin wrote:
> On Sat, May 29, 1999 at 02:30:16PM +0100, Chris Butler wrote:
> > A program I'm currently thinking of packaging (nessus, a network
> > administration tool similar to SATAN)
> You shouldn't :) Javier Pena and me are already interested in it,
> and we almost have the package ready. It is possible that Javier's
> package is already accepted in the archive by now...
Well, as a matter of fact is Javier Fernandez-Sanguino Peña :) And
yes, nessus is sitting in Incoming, waiting to be accepted, you can get a
Try it if you will.
> > has optional support for
> > cryptography which would put the client and server programs into
> > non-US.
> > However, since this support is optional, should I also provide a
> > non-crypto enabled version for main?
> > AIUI, this would mean that I have to create a seperate source package
> > that contains no crypto hooks at all, instead of just creating two
> > binaries with and without the cryptography enabled.
> > So my question is, should I provide a non-crypto enabled version, and
> > if so, do I need to have seperate source packages?
> Two sources are definitely needed, however, I don't know whether we
> actually need to change the US one to exclude anything crypto related.
> I'm CC:ing also our -legal team, which should know what to do.
Im not sure about that, US law will nowt allow distribution of
strong criptography, but nessus, as far as I know does not use *strong*
criptography, but someone should check the sources. ¿anyone?
> enJoy -*/\*- http://jagor.srce.hr/~jrodin/
If it does use 128 bit criptography it should have tow sources,
the version I packaged, however (990201) currently does not provide two
packages ,anyone can help?