On Tue, Jul 16, 2002 at 11:39:41PM -0600, Eric Anholt wrote:
> > I thought the whole point of Wraphelp.c was that the person who
> > runs the machine (whatever machine X is being installed on) has
> > to obtain that file, so they would have to explicitly verify that
> > they -- personally -- have the right to use it.
> > 
> > Mind you, I did that once about seven years ago, and I just keep
> > copying that Wraphelp.c around to wherever I need it.  I have no
> > idea what the current requirement is...   :-)
> It used to be that way.  Then within the last year (iirc) our ports
> changed to auto-downloading Wraphelp.c and defaulting to HasXdmAuth
> YES.  I don't know what exactly changed legally.  I noted that at least
> NetBSD has a Wraphelp.c in their CVS repos of X-3 and X-4.
> My changes do make the file required by all of the miniports that could
> use it, though it only gets used if HasXdmAuth is set to YES by imake-4
> (it's default).

If you'll read the commit log which made this change, you'll see
that I was the one who changed this.  I did so after consulting
with core regarding the current export rules of the USA.  The BXA
(Bureau of Export Administration) loosened their rules for
cryptographical software export last year (or the year before, I
don't remember exactly), and so open source software is only
required to register with the BXA if they export cryptographic
software.  FreeBSD did that many years ago, so I removed the need
for somebody to fetch that file if they want XDM-AUTHORIZATION-1.
I'd like to point out that Wraphelp.c performs DES encryption,
and we have already done that out of the box for quite some time.

See http://www.bxa.doc.gov/ for more info.  [Seems they changed
their name to Bureau of Industry and Security...]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to