Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Crypto problems again
Date: Mon, 02 Feb 2004 19:54:16 +0100	[thread overview]
Message-ID: <ilu7jz5wbvr.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m31xpd2wc1.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 02 Feb 2004 19:02:54 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I've just had a mail from Stallman about crypto-related code in
> Gnus.  He wants the crypto code out of Emacs (due to the
> still-lingering crypto export restrictions in the US).  (I thought
> those problems were gone by now, but apparently not.)
>
> So we need to compile a list of crypto-related files and functions in
> Gnus, so that Stallman can remove those from the Emacs distribution...
>
> Most of the crypto code was added post Gnus 5.9, so there might not
> be all that much to remove, but I'm not intimately familiar with the
> crypto code.

What's the definition of crypto code?  For example, does an elisp
wrapper around GnuTLS count?  A wrapper around GnuPG?  Emacs contains
a MD5 implementation in C, is it "crypto"?  Or MD4, SHA-1?  Are
authentication mechanisms based on hashing, like CRAM-MD5, "crypto"?

In any case, files that may be relevant to look at include (not all
might have been part of Gnus 5.9):

ntlm.el
pgg*.el
sasl*.el
md4.el
hmac-*.el
imap.el
sieve-manage.el
tls.el
starttls.el
sha1-el.el
pop3.el
mml-sec.el
mml-smime.el
mml1991.el
mml2015.el
canlock.el
netrc.el



  reply	other threads:[~2004-02-02 18:54 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 [this message]
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
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=ilu7jz5wbvr.fsf@latte.josefsson.org \
    --to=jas@extundo.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).