Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Crypto problems again
Date: Thu, 05 Feb 2004 15:09:46 -0500	[thread overview]
Message-ID: <4nznbxuw39.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <m3ad3xl9qo.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 05 Feb 2004 18:25:03 +0100")

On Thu, 05 Feb 2004, larsi@gnus.org wrote:

> And here's the response from RMS:
> 
> ----------
> 
>     What's the definition of crypto code? 
> 
> I will explain how I understand the matter.  However, why ask me
> when you can learn from experts?  There must be web sites that
> explain this issue in detail.  I don't know which sites, but you can
> find them more easily than I can.

Bah, this makes no sense.  There's a clear distinction between
trivial ciphers, such as ROT-13 and the XOR cipher I put into
gnus-encrypt.el, and strong crypto.  Is Base64 crypto?  UUdecode?

Going to web sites is nice, but does not answer the questions.  I
hope RMS can assign someone specific to look at the particular issues
in Gnus instead of what he suggests above.

Considering code that wraps around a crypto program also crypto is
even stranger, IMHO.  It really complicates life needlessly.

Anyhow, I can make gnus-encrypt.el optional, and the functions it
provides can be defined as empty wrappers in gnus.el, overridden if
you explicitly load gnus-encrypt.el.  Would that be OK?

Thanks
Ted



  parent reply	other threads:[~2004-02-05 20:09 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 [this message]
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=4nznbxuw39.fsf@collins.bwh.harvard.edu \
    --to=tzz@lifelogs.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).