From: Ted Zlatanov <tzz@lifelogs.com>
Subject: crypto in netrc.el and gnus-encrypt.el (was: Crypto problems again)
Date: Mon, 02 Feb 2004 14:49:30 -0500 [thread overview]
Message-ID: <4nfzdt1ctx.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <m31xpd2wc1.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 02 Feb 2004 19:02:54 +0100")
I'm also unsure (like Simon) about what's considered crypto code. In
any case, netrc.el wraps around OpenSSL right now, but that will be
removed as soon as I put gnus-encrypt.el into Gnus. So netrc.el is
not crypto code by any measure.
gnus-encrypt.el has a built-in XOR cipher which is very simple, I
doubt that's considered strong encryption. It may use encryption
ciphers from gencrypt.el, which is not written yet, but I don't plan
to add any strong ciphers to gnus-encrypt.el. I may add an encoding
cipher, which won't even encrypt anything. Does that help?
By the way, gnus-encrypt.el is working pretty well for me so I'll be
putting it into Gnus soon, together with support in netrc.el. I hope
that's OK with everyone.
Ted
next prev parent reply other threads:[~2004-02-02 19:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 18:02 Crypto problems again 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 ` Ted Zlatanov [this message]
2004-02-02 23:05 ` 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=4nfzdt1ctx.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).