Bug 1126 - wraphelp.c not in distribuition...
Summary: wraphelp.c not in distribuition...
Alias: None
Product: xorg
Classification: Unclassified
Component: App/xdm (show other bugs)
Version: git
Hardware: All All
: high major
Assignee: Xorg Project Team
QA Contact:
Depends on:
Blocks: 999
  Show dependency treegraph
Reported: 2004-08-18 12:34 UTC by Jim Gettys
Modified: 2004-09-08 20:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Jim Gettys 2004-08-18 12:34:38 UTC
Causing lost time and effort for people, who can't have their authentication


I've put in the mail the crypto letters required by the U.S. Government
for exporting cryptography, for xdm, as a member of X.org's BOD.
I notified them both of ftp.x.org and www.freedesktop.org, since we do
our development on fd.o and often release software there as well (not to
mention the CVS repository).

See: http://www.debian.org/legal/cryptoinmain for lots of useful
information and the legal opinion given to the Debian project. I've
gotten the same information internally in HP that matches the opinion
that Debian paid to have done.  Note that this situation is for open
source work; if you work for a company that does products containing
crypto, you still have to follow the commercial rules on the topic.

For this X.org release:
  1) we need to commit the wraphelp.c file of whatever version is
appropriate for xdm.
  2) Notification is needed.
	o We need to add the notice below to the website 
	o with our release itself in the FTP directory. 
	o I'd put it in the top of any tarball we generate that 
	contains crypto.
	o I'd also add it to a readme file next to wraphelp.c just to
	 be complete,
	o have a pointer from any fd.o project containing crypto 
	to the notice.
I think that will cover all the bases.

For the future: if we add *additional* programs/libraries to the
distribution/web site/archive, we are supposed to draft and send in new
letters the first time we distribute them.  See the above link for

Note that this is true for freedesktop.org as well; letters should be
sent in whenever new crypto appears.  The letters are reasonably
painless to deal with.

We do not have to notify for every release or change, nor do we have to
wait until we hear from the government having sent in the letters. 
Binaries compiled from the source can also be redistributed freely.

If the notice is put into the wiki, it should be locked somehow so that
it can't be trivially changed, I suspect.

And if you think this is a bit silly, you aren't alone.  But at least we
can integrate/export the code and binaries these days without too much
Comment 1 Jim Gettys 2004-08-20 19:10:40 UTC
Ok, I picked up the australian version, and committed it, along with
notification files.

I did pretty simple editing to make it compile cleanly, rather than half
a dozen warnings.

This version implemented, was obtained by anonymous ftp to ftp.psy.uq.oz.au
( in the directory /pub/X11R5/. written by
eric eay@psych.psy.uq.oz.au
Comment 2 Jim Gettys 2004-08-21 10:34:43 UTC
I forgot to move this over to the release note bug.
Comment 3 Jim Gettys 2004-09-09 13:22:46 UTC
All done.  with some bobbles, it should now be working...

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.