Re: DES module in kernel?

Mike Eisler (mre@eng.sun.com)
Tue, 16 Mar 1999 19:06:39 -0800 (PST)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: David Hinds: "Ideas for abstracting driver IO from bus implementation?"
Previous message: Mike Shaver: "PPP and 2.2.3 Failure"
In reply to: Brian Macy: "Re: 2.2.3 lock with AppleTalk DDP..."

> > Whoever is "in charge" of Linux will need to seek legal counsel
> > versed in these issues. The U.S. has relaxed export control laws,
> > and so export of 56 bit DES is possible (I've done it), and legal,
> > but only with an appropriate export control license.
> >
> > I can provide the name of a competent attorney, if anyone is interested.
> > It is possible to get export control licenses without legal assistance,
> > but it's no doubt easier to have a point person who works a few minutes
> > away from the relevant gov't agencies in the D.C. area.
>
> The problem is that there *is* no such "in charge" person, and such
> the regulations are highly skewed in favour of companies. These
> regulations are deadly for Open Source projects.

Individuals can export products; there's no requirement that I know of
that an incorporated body apply for a crypto export license. Really, anyone
who wants to take the initiative can, even if Linux is truly a commons.

-mre

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: David Hinds: "Ideas for abstracting driver IO from bus implementation?"
Previous message: Mike Shaver: "PPP and 2.2.3 Failure"
In reply to: Brian Macy: "Re: 2.2.3 lock with AppleTalk DDP..."