Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: file encryption in Gnus: a roadmap attempt
Date: Wed, 21 Apr 2004 11:58:50 -0400	[thread overview]
Message-ID: <4nr7uhgw5h.fsf@lifelogs.com> (raw)

After a lengthy discussion on emacs-devel, here's my plan for adding
encryption to Gnus:

1) move what I used to call "gnus-encrypt.el" to "gencrypt.el" which
   will be an ELisp package maintained by me and/or others.

2) write a gnus-file.el package, which will provide generic hooks for
   all interesting Gnus file I/O; for instance newsrc.el will use it.

3) write code in gencrypt.el which will install encryption hooks into
   the gnus-file hooks.

This has to be done because of Emacs export restrictions.

I am trying to avoid writing a user-transparent file I/O layer;
gencrypt.el should be an API and then the file I/O layer can be built
on top, possibly inside gencrypt.el as well.

The most common question was, "why not just use file handlers"?  An
API allows much more control than file handlers, and can be
guaranteed not to interfere with other file handlers.  My experience
with crypt++.el has led me to avoid file handlers as a baseline
feature for encryption specifically.

Please let me know if you have questions and/or comments.

Ted



             reply	other threads:[~2004-04-21 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 15:58 Ted Zlatanov [this message]
2004-04-24 15:53 ` 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=4nr7uhgw5h.fsf@lifelogs.com \
    --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).