Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: encrypt.el glue to PGG library added (was: emacs->gnus merge questions)
Date: Tue, 18 Dec 2007 16:52:51 -0600	[thread overview]
Message-ID: <86wsrblinw.fsf_-_@lifelogs.com> (raw)
In-Reply-To: <86bq8nn41i.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 18 Dec 2007 14:25:45 -0600")

I added an encrypt.el option (for encrypt-file-alist) to use PGG as the
encode/decode option.  It currently only uses the symmetric
functionality and lets PGG do all the cipher and passphrase management.
If you want me to add more PGG glue, let me know.

I also reworked the encrypt.el API to be a bit nicer, using more
temporary buffers in a few places.

Please let me know if you need anything in the encrypt.el library.  I
currently use it to keep my NNTP, SMTP, IMAP, POP, etc. passwords
encrypted in a single place with netrc.el.  If you can think of any
other places in Gnus where encryption would make sense, let me know.

Thanks
Ted



  reply	other threads:[~2007-12-18 22:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08  3:24 emacs->gnus merge questions Miles Bader
2007-12-08 19:38 ` Reiner Steib
2007-12-08 21:19   ` Miles Bader
2007-12-08 21:29     ` Reiner Steib
2007-12-08 23:32   ` Miles Bader
2007-12-08 23:45   ` Miles Bader
2008-02-16 13:24     ` encrypt.el (was: emacs->gnus merge questions) Reiner Steib
2008-02-16 13:26     ` assistant.el " Reiner Steib
2007-12-11 16:22   ` emacs->gnus merge questions Ted Zlatanov
2007-12-17 23:02     ` Ted Zlatanov
2007-12-17 23:03       ` Ted Zlatanov
2007-12-18 20:25       ` Ted Zlatanov
2007-12-18 22:52         ` Ted Zlatanov [this message]
2008-02-16 13:12       ` encrypt.el (was: emacs->gnus merge questions) Reiner Steib
2008-02-28 14:55         ` encrypt.el Ted Zlatanov
2008-02-28 20:28           ` encrypt.el Reiner Steib
2008-03-10 15:06             ` encrypt.el Ted Zlatanov

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=86wsrblinw.fsf_-_@lifelogs.com \
    --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).