Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Crypto problems again
Date: Fri, 06 Feb 2004 01:24:39 +0100	[thread overview]
Message-ID: <m3d68t9hrs.fsf@defun.localdomain> (raw)
In-Reply-To: <sd4qu5glz6.fsf@wes.hardakers.net> (Wes Hardaker's message of "Thu, 05 Feb 2004 15:11:57 -0800")

Wes Hardaker <wes@hardakers.net> writes:

>>>>>> On Thu, 05 Feb 2004 23:18:46 +0100, Jesper Harder <harder@ifa.au.dk> said:
>
> Jesper> We recommend that you perform IP checking and deny downloads
> Jesper> to known embargoed countries. This due diligence also would
> Jesper> provide a defense to a claim of civil liability. If you find
> Jesper> out that your software has been downloaded to a prohibited
> Jesper> destination, then I recommend that you block future downloads
> Jesper> to that specific site unless and until you obtain a license
> Jesper> from BXA.
>
> That last part seems to imply that after you get a license you should
> release the block.  This paragraph makes no sense, since you can't do
> the first part until after you write BXA and the second part isn't
> required after you write the BXA.

I think what they mean is:

  If you become aware that an evil Taleban is downloading cryptoEmacs,
  you should block his IP unless you obtain permission to export it to
  Taleban controlled Afghanistan.  You won't get this permission, of
  course, so the IP should stay blocked.

> It's almost written like an opinion that even though you can release
> it to one of the 7 evil countries of the world (TM) (or is it now 5
> since we took over 2 of them?) you shouldn't do so because it would
> be morally wrong.

I don't think that's the intent.  It might make more sense if you read
the context, <http://www.debian.org/legal/cryptoinmain> near the
bottom.



  reply	other threads:[~2004-02-06  0:24 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-02 18:02 Lars Magne Ingebrigtsen
2004-02-02 18:54 ` Simon Josefsson
2004-02-02 23:07   ` Wes Hardaker
2004-02-03  9:12   ` Lars Magne Ingebrigtsen
2004-02-05 17:25     ` Lars Magne Ingebrigtsen
2004-02-05 17:45       ` Wes Hardaker
2004-02-05 20:09       ` Ted Zlatanov
2004-02-05 20:53       ` Simon Josefsson
2004-02-05 21:37         ` Wes Hardaker
2004-02-06  0:53         ` Jesper Harder
2004-02-05 21:29       ` Josh Huber
2004-02-05 21:38         ` Wes Hardaker
2004-02-05 22:36       ` Simon Josefsson
2004-02-05 23:09         ` Wes Hardaker
2004-02-02 19:49 ` crypto in netrc.el and gnus-encrypt.el (was: Crypto problems again) Ted Zlatanov
2004-02-02 23:05 ` Crypto problems again Wes Hardaker
2004-02-05 21:22   ` Jesper Harder
2004-02-05 21:39     ` Wes Hardaker
2004-02-05 22:18       ` Jesper Harder
2004-02-05 23:11         ` Wes Hardaker
2004-02-06  0:24           ` Jesper Harder [this message]
2004-02-06  1:47 ` Jesper Harder
2004-02-06 15:42   ` Wes Hardaker
2004-02-06 23:58     ` Jesper Harder
2004-02-09 21:03       ` Ted Zlatanov
2004-02-13 10:17         ` Kai Grossjohann

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=m3d68t9hrs.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    /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;
as well as URLs for NNTP newsgroup(s).