DOC obstructs encryption export again - Non USA crypto base again ?

Julian H. Stacey jhs at
Tue Oct 21 14:52:12 UTC 2014

How can FreeBSD best re-segregate crypto components of its repository again,
ready to move crypto components outside the USA, as USA DOC imperils again ?

FreeBSD is now SVN based, we were CVS last time,  Any new issues to solve  ?
Can smooth transition be planned before, in case of risk of USA DOC action ?

Last time FreeBSD used South Africa; if that's not viable, 
FreeBSD based servers elsewhere are available (including in .EU).
    "US government fines Intel's Wind River over crypto exports"

    "Now, as Techdirt notes, the conflict between government
    regulation and the tech industry is moving onto the renal
    original turf of the first crypto wars of the late 90s - the
    export of strong encryption."

    "For those who lived through the late 90's cryptowars, it's
    beginning to feel like history is repeating itself."
    "maybe the decision to keep GnuPG infrastructure out of the US
    - even after the lifting of the export restrictions - was not too bad."

USA Dept. of Commerce were obstructive idiots even back in the early 1980s: 
  (DOC obstructed delivery of Unix systems with crypt binary (not
  source), though British Unix source licencees, associates, &
  even the communist East were all in possesion of crypt.c source

With raised world tensions on many fronts, DOC crypto export obstruction
will presumably increase, with NSA encouraging DOC.

A non USA base for crypto parts of the FreeBSD repository would
again safeguard the world FreeBSD community from the whims of the
USA DOC, & remove or reduce risk of USA prosecution of USA FreeBSD
administrators & cryptographic developers.

Julian Stacey, BSD Linux Unix'78 C Sys Eng Consultant Munich
 Indent previous with "> ".  Interleave reply paragraphs like a play script.
 Send plain text, not quoted-printable, HTML, base64, or multipart/alternative.

More information about the freebsd-hackers mailing list