Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Rafferty <craffert@ms.com>
Subject: Re: MIME and mailcrypt
Date: 04 Dec 1998 17:53:25 -0500	[thread overview]
Message-ID: <vgvpv9zcye2.fsf@ms.com> (raw)
In-Reply-To: Stainless Steel Rat's message of "04 Dec 1998 16:38:08 -0500"

Stainless Steel Rat writes:
> "Hrvoje" == Hrvoje Niksic <hniksic@srce.hr> writes:

Hrvoje> Yes; that's how TM is reported to work.  Adding this to Gnus now
Hrvoje> remains a small matter of programming.  Would such an addition
Hrvoje> really be illegal to export from the US?

> Yes, it is.  The way the Department of Justice got ITAR (International
> Trade in Arms Regulations) worded, it is functionality that is restricted.
> Although the DoJ seems to turn a blind eye to hooks, so long as the strong
> crypto is either not there or disabled.  To wit, Netscape Navigator export
> versions, which can be trivially patched to use 128-bit keys instead of
> 40-bit keys.

Then doesn't this mean that Gnus w/mailcrypt is still legal to export, 
since it actually isn't doing encryption, but calling a program that
does it for you.

Really, mailcrypt (and Gnus calling it) is only a hook.  We could tack 
on a weak encryption program, or a strong one -- it wouldn't be able
to tell the difference.

> Then again, there is the fact that if the code is written outside the US,
> the DoJ can't bitch about it (which is what we did for PGP 2.3 and 2.3a).

This doesn't matter, since we cannot re-export it from xemacs.org (in
the US).  It would really suck to have a part of XEmacs not under the
same cvs tree as the rest.

-- 
Colin


  parent reply	other threads:[~1998-12-04 22:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <x7yaortjhy.fsf@peorth.gweep.net>
1998-12-02 17:06 ` Lars Magne Ingebrigtsen
     [not found]   ` <x7pva21h57.fsf@peorth.gweep.net>
1998-12-02 23:57     ` Kai.Grossjohann
     [not found]       ` <x71zmixan9.fsf@peorth.gweep.net>
1998-12-03  2:21         ` Hrvoje Niksic
1998-12-03  8:46         ` Jari Aalto+list.ding
1998-12-03 10:38         ` Kai.Grossjohann
1998-12-03 11:35     ` Lars Magne Ingebrigtsen
     [not found]       ` <x767btkll7.fsf@peorth.gweep.net>
1998-12-04  2:09         ` Lars Magne Ingebrigtsen
     [not found]           ` <x7n25462fl.fsf@peorth.gweep.net>
1998-12-04  4:08             ` Lars Magne Ingebrigtsen
1998-12-09 22:48           ` Dave Love
1998-12-04  2:49         ` Stephen Zander
     [not found]           ` <x71zmfapi8.fsf@peorth.gweep.net>
1998-12-04 16:10             ` Karl Kleinpaste
1998-12-04 16:32             ` Hrvoje Niksic
     [not found]               ` <x7r9ufzv38.fsf@peorth.gweep.net>
1998-12-04 18:22                 ` Hrvoje Niksic
1998-12-04 18:49                   ` David S. Goldberg
     [not found]                   ` <x7af13hbfs.fsf@peorth.gweep.net>
1998-12-04 21:03                     ` Hrvoje Niksic
     [not found]                       ` <x7zp93fv0f.fsf@peorth.gweep.net>
1998-12-04 22:53                         ` Colin Rafferty [this message]
     [not found]                           ` <x7ogpj5tyv.fsf@peorth.gweep.net>
1998-12-05 16:09                             ` Lars Magne Ingebrigtsen
1998-12-06 19:47                               ` Dave Love
     [not found]                                 ` <x7u2z9ni5s.fsf@peorth.gweep.net>
1998-12-09 22:43                                   ` Dave Love
1998-12-04 22:54                         ` Hrvoje Niksic
1998-12-04 23:08                           ` Colin Rafferty
     [not found]                             ` <x7yaon5vtv.fsf@peorth.gweep.net>
1998-12-08  2:10                               ` Stephen Zander

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=vgvpv9zcye2.fsf@ms.com \
    --to=craffert@ms.com \
    /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).