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: Thu, 08 Jan 2004 17:03:39 -0500 [thread overview]
Message-ID: <4nisjmhzd0.fsf@collins.bwh.harvard.edu> (raw)
In-Reply-To: <m3d69w31vn.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 07 Jan 2004 03:53:48 +0100")
On Wed, 07 Jan 2004, larsi@gnus.org wrote:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> I think I'd like to start on gnus-encrypt.el. These functions will
>> be available:
>>
>> gnus-encrypt-insert-file-contents
>> gnus-encrypt-write-file-contents
>
> These sound so generic and useful that I think it would make sense
> to just create encrypt.el and call them
> `encrypt-insert-file-contents', etc.
OK, here's the plan.
The crypt++.el package, which does a lot of what I need to do, will
be the starting point. I'll call my package gencrypt.el. I talked
to Karl Berry, the current crypt++.el maintainer, and he's OK with
this.
Gnus will get gnus-encrypt.el which will use
gencrypt-insert-file-contents (+ arguments)
gencrypt-write-file-contents (+ arguments)
to provide
gnus-encrypt-insert-file-contents (no arguments if possible)
gnus-encrypt-write-file-contents (no arguments if possible)
using the gnus-encrypt-file-alist association list we discussed.
This will let Gnus internals move to using the gnus-encrypt.el
functions without modifications.
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.
Ted
next prev parent reply other threads:[~2004-01-08 22:03 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 [this message]
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
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=4nisjmhzd0.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).