Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: authinfo/netrc file encryption status -- GnuPG
Date: 23 Jul 2004 12:22:38 -0400	[thread overview]
Message-ID: <4nwu0u8zht.fsf@lifelogs.com> (raw)
In-Reply-To: <jk4k6wx8bfu.fsf@W003275.na.alarismed.com> (Steven E. Harris's message of "Wed, 21 Jul 2004 11:25:25 -0700")

On Wed, 21 Jul 2004, seh@panix.com wrote:

> Back in January, we had a round of discussion about adding encryption
> support of authinfo files. That discussion then generalized into
> adding encryption support for any type using a set of encryption tools
> such as GnuPG and OpenSSL.¹
> 
> In May, Ted Zlanatov posted gnus-encrypt.el.² I just noticed that this
> file is still not part of Gnus in CVS. What's the status on this
> integration? Should I grab gnu-encrypt.el and start testing it, or has
> it been superseded by some other effort?
> 
> My main interest is in encrypting ~/.authinfo with gpg using a
> symmetric cipher. I recall that Ted had this working, but lost track
> of why the code hasn't yet become a blessed part of Gnus.

The current gnus-encrypt.el is attached.  I have plans to write
gencrypt.el which will do a lot more, and will involve changes to
gnus-encrypt.el, but by that time gnus-encrypt.el will be in CVS
anyhow.  So take a look and let me know if it works for you as it
is.  Just call the functions gnus-encrypt-insert-file-contents and
gnus-encrypt-write-file-contents directly after customizing
gnus-encrypt-file-alist.

As of now, netrc.el also has encryption support with OpenSSL, which
will be removed once gnus-encrypt.el is in place.  So don't use that.

The BIG delay, by the way, was because nothing in Emacs was allowed
to contain crypto code or even call crypto software.  That has been
resolved as of May 2004, so gnus-encrypt.el should be OK for
inclusion if people are happy with it.  I meant to work on
gnus-encrypt.el back then but have been too busy - so if anyone wants
to help, they're welcome to it.

Thanks
Ted



  reply	other threads:[~2004-07-23 16:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-21 18:25 Steven E.Harris
2004-07-23 16:22 ` Ted Zlatanov [this message]
2004-07-23 17:16   ` Steven E. Harris
2004-07-23 17:00     ` Ted Zlatanov
2004-07-23 21:39   ` Steven E. Harris
2004-07-27 16:56     ` Ted Zlatanov
2004-07-27 18:12       ` Steven E. Harris
2004-07-30 16:52         ` Ted Zlatanov
2004-08-02 23:06           ` Jeremy Maitin-Shepard
2004-08-03 17:09             ` Ted Zlatanov
     [not found]           ` <jk465858idw.fsf@W003275.na.alarismed.com>
     [not found]             ` <4n4qnl8mnw.fsf@lifelogs.com>
     [not found]               ` <jk4ekmp1iym.fsf@W003275.na.alarismed.com>
2004-08-03 17:11                 ` Ted Zlatanov
2004-08-03 21:47                   ` Steven E. Harris
2004-08-04 16:54                     ` authinfo encryption through netrc.el works now (was: authinfo/netrc file encryption status -- GnuPG) Ted Zlatanov
2004-08-04 17:55                       ` authinfo encryption through netrc.el works now Simon Josefsson
2004-08-05 22:09                         ` Ted Zlatanov
2004-08-06 17:43                           ` Ted Zlatanov
2004-08-06 18:07                             ` Simon Josefsson
2004-08-04 18:37                       ` Steven E. Harris
2004-08-05 22:05                         ` Ted Zlatanov
2004-08-05 22:59                           ` Steven E. Harris
2004-08-06 17:45                             ` Ted Zlatanov
2004-08-06 18:18                               ` Simon Josefsson
2004-08-06 21:57                                 ` Ted Zlatanov
2004-08-04 22:55                   ` authinfo/netrc file encryption status -- GnuPG Steven E. Harris
2004-08-06 17:31                     ` 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=4nwu0u8zht.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).