From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Guidance on distributed patented software
Date: Mon, 27 Sep 2021 17:09:08 -0400 [thread overview]
Message-ID: <CAGfcS_myX+=Hr75orD-3=dvTSTMY7T=+nA3ktyntzbK-SyvZ-w@mail.gmail.com> (raw)
In-Reply-To: <f6cef3a6-e8b3-f375-e088-354dcded09fa@gentoo.org>
(This is all tangential to the main issue of this thread and just
discussing internet history - skip as you wish...)
On Mon, Sep 27, 2021 at 2:14 PM Marek Szuba <marecki@gentoo.org> wrote:
>
> I am no expert on US law but from what I have read (in many different
> sources, with me having begun using PGP in either late 1996 or early
> 1997 i.e. when it was still very much subject to US export restrictions)
> about this case, both the publishing of the source-code book and it
> having subsequently been taken out of the country has been legal - the
> former due to publishing the first amendment
Well, based on the little I know of US export controls, I doubt that
being in book form vs some other form really has any bearing in
principle.
HOWEVER, I think it was probably done specifically as a challenge to
the constitutionality of the law. Ie, the argument would be that it
ought to be legal to take the source code out in any form. By doing
it via a formally published book though they take away all the "exotic
internetness" out of the equation and this way all the 60 year old
judges (in the 90s) who might get involved are forced to confront it
as suppression of book distribution. In principle though I think most
of us would agree that there is no difference in sharing information
no matter the way in which it is conveyed. It was probably their hope
that if it did go to court any ruling that secured the right to
distribute via book could then be leveraged against other modes.
I'm guessing that it was never challenged in court precisely for this
reason. US export controls cover the communication of information via
any mode:
https://www.bis.doc.gov/index.php/policy-guidance/deemed-exports
If they had fought the export of this book it is quite possible that
there would have been a ruling that just finds all export controls to
be illegal. Really when you think about it any sort of restriction on
communication of classified information or whatever is going to run
into the 1st amendment. Courts are going to tend to make their
rulings on what can be restricted narrow as a result. The government
probably prefers to maintain some FUD around where those boundaries
lie, to get companies in particular to follow policies that in the end
might not be enforceable. (Note I'm not arguing that dissemination of
classified info ought to be legal, but as you move away from things
like locations of troops or blueprints of specific aircraft or
whatever, into more generic topics like entire classes of technology,
I think you're going down a slippery slope...)
The main reason that all of this went away though was that I think it
was Clinton that specifically granted an exception to cryptography
software from ITAR. The concerns were that the cat was basically out
of the bag anyway, and consumers were potentially going to be harmed
by things like web browsers getting distributed with 40-bit key
limitations. Sure, secure browsers were also probably available to
people who knew the right links to click, but do we really want
somebody reputable like Google to end up having to have a link on
their website for a non-secure version of their software, and where
the non-secure link just gives you a download, while the secure link
makes you jump through hoops to verify your location/etc? The popular
use of SSL for entering credit card info on e-commerce sites really
was what drove it IMO.
--
Rich
next prev parent reply other threads:[~2021-09-27 21:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 16:46 [gentoo-dev] Guidance on distributed patented software Alec Warner
2021-09-20 17:27 ` Rich Freeman
2021-09-20 18:15 ` Robin H. Johnson
2021-09-20 18:41 ` Ulrich Mueller
2021-09-20 19:20 ` Robin H. Johnson
2021-09-22 12:54 ` Joshua Kinard
2021-09-22 16:37 ` Robin H. Johnson
2021-09-23 5:54 ` Joshua Kinard
2021-09-23 15:52 ` Peter Stuge
[not found] ` <CAAr7Pr9a6cRbHDxkUbKwxabW8skh1izA7C2GqTE1XF8mg-CV0g@mail.gmail.com>
2021-09-24 7:46 ` Joshua Kinard
[not found] ` <20210924095510.6ff13620@computer>
2021-09-25 19:44 ` Joshua Kinard
2021-09-26 17:09 ` Peter Stuge
2021-09-26 19:20 ` Rich Freeman
2021-09-27 18:14 ` Marek Szuba
2021-09-27 21:09 ` Rich Freeman [this message]
2021-09-26 19:41 ` Sam James
2021-09-21 15:25 ` Andreas K. Huettel
2021-09-20 18:30 ` [gentoo-dev] " Ulrich Mueller
2021-09-26 6:38 ` Alec Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_myX+=Hr75orD-3=dvTSTMY7T=+nA3ktyntzbK-SyvZ-w@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox