From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Karl Berry <karl@freefriends.org>, kyle_jones@wonderworks.com
Subject: Re: netrc.el now supports encoded files
Date: Tue, 27 Jan 2004 14:44:42 -0500 [thread overview]
Message-ID: <4nektljhw5.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <4nisjmhzd0.fsf@collins.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 08 Jan 2004 17:03:39 -0500")
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
On Thu, 08 Jan 2004, tzz@lifelogs.com wrote:
> Without gencrypt.el, gnus-encrypt.el will provide four options:
> OpenSSL encoding (I'll just copy what I have in netrc.el), GPG
> encoding (simple command-line invocation with --armor), base64
> encoding, and no encoding.
I've finished the GPG and one built-in cipher for gnus-encrypt.el.
Attached is the code. I need a few people to test it, and any
feedback is appreciated of course. OpenSSL and base64 encodings were
not implemented because I didn't think they were really necessary.
OpenSSL support will probably come through gencrypt.el when that's
released.
If the *encoding* fails, the file is saved in plain text.
If the *decoding* fails, we load the encoded file. Tough break.
The built-in XOR filter is actually pretty nice. It's not good
encryption, but it's definitely a step up from base64, and it had
decent speed when I tried it.
The major issue is that, for simplicity, gnus-encrypt.el only works
with whole buffers. I don't think more will be necessary for Gnus
development, although the gencrypt.el code will definitely support
encoding of regions and such.
If and when gnus-encrypt.el goes into the Gnus CVS, I will start
adding support for it everywhere in Gnus. Without setting
gnus-encrypt-file-alist, users will see absolutely no effect from the
gnus-encrypt functions.
Ted
[-- Attachment #2: gnus-encrypt.el --]
[-- Type: application/emacs-lisp, Size: 8436 bytes --]
next prev parent reply other threads:[~2004-01-27 19:44 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 [this message]
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
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=4nektljhw5.fsf@collins.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=karl@freefriends.org \
--cc=kyle_jones@wonderworks.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).