From: Ted Zlatanov <tzz@lifelogs.com>
Cc: "Ding Mailing List" <ding@gnus.org>
Subject: Re: netrc.el now supports encoded files
Date: Tue, 06 Jan 2004 14:58:58 -0500 [thread overview]
Message-ID: <4n8ykkzw59.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <2268.217.208.174.213.1073395735.squirrel@217.208.174.213> (Simon Josefsson's message of "Tue, 6 Jan 2004 14:28:55 +0100 (CET)")
On Tue, 6 Jan 2004, jas@extundo.com wrote:
> IMHO, use GnuPG instead of OpenSSL. I'm trying to remove the last
> OpenSSL dependencies from Gnus (ssl.el and sha1-el.el are done, I'm
> working on starttls.el, smime.el is the next step). Perhaps
> supporting OpenSSL as well is OK, but I think the defaults should be
> to use GNU tools where available.
Sure. I don't use GnuPG, so if someone who does could give me the
command lines I'll be glad to add the Lisp code to netrc.el.
Actually I may move it all to gnus-encrypt.el or something like that.
> I wrote an elisp AES implementation some time ago
> (<http://josefsson.org/aes/>) but I'm not sure using it is a good
> idea, password based file encryption is more complicated than the
> block cipher primitive.
That looks useful in theory, but it's very slow. I was hoping for a
faster cipher. Should I just turn down rijndael-monte-carlo-limit
and rijndael-monte-carlo-loop or would that make the cipher
significantly less secure? I don't know AES so I can't judge that.
The interface is pretty complicated (the string and key lengths are
limited). Can we have a simple encrypt/decrypt function?
rijndael.el is not (currently) part of Gnus or Emacs, is that a
problem? How should I connect it to gnus-encrypt.el, with autoloads?
Sorry for the many questions :)
Thanks
Ted
next prev parent reply other threads:[~2004-01-06 19:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 23:22 Ted Zlatanov
2004-01-05 23:34 ` Jesper Harder
2004-01-06 1:02 ` Ted Zlatanov
2004-01-06 0:13 ` Steven E. Harris
2004-01-06 1:01 ` Ted Zlatanov
2004-01-06 21:57 ` Chris Green
2004-01-06 23:00 ` Ted Zlatanov
2004-01-06 23:25 ` Simon Josefsson
2004-01-06 23:58 ` Ted Zlatanov
2004-01-07 0:09 ` Simon Josefsson
2004-01-07 2:53 ` Lars Magne Ingebrigtsen
2004-01-08 22:03 ` Ted Zlatanov
2004-01-27 19:44 ` Ted Zlatanov
2004-01-07 14:47 ` Chris Green
2004-01-08 20:48 ` Ted Zlatanov
2004-01-06 13:28 ` Simon Josefsson
2004-01-06 19:58 ` Ted Zlatanov [this message]
2004-01-06 20:24 ` Simon Josefsson
2004-01-06 20:59 ` Steven E. Harris
2004-01-06 22:00 ` Simon Josefsson
2004-01-06 22:24 ` Simon Josefsson
2004-01-06 22:56 ` Ted Zlatanov
2004-01-06 23:13 ` Ted Zlatanov
2004-01-06 23:35 ` Simon Josefsson
2004-01-06 20:33 ` Simon Josefsson
2004-01-06 23:14 ` Ted Zlatanov
2004-01-06 23:19 ` Richard Hoskins
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=4n8ykkzw59.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).