From: "Steven E. Harris" <seh@panix.com>
Subject: Re: authinfo/netrc file encryption status -- GnuPG
Date: Fri, 23 Jul 2004 14:39:24 -0700 [thread overview]
Message-ID: <jk4iscecsj7.fsf@W003275.na.alarismed.com> (raw)
In-Reply-To: <4nwu0u8zht.fsf@lifelogs.com>
"Ted Zlatanov" <tzz@lifelogs.com> writes:
> The current gnus-encrypt.el is attached.
Thanks.
> So take a look and let me know if it works for you as it is.
So far, I noticed that `make-temp-file' (used in
gnus-encrypt-gpg-process-buffer) does not exist in XEmacs. I used
`make-temp-name' instead.
> Just call the functions gnus-encrypt-insert-file-contents and
> gnus-encrypt-write-file-contents directly after customizing
> gnus-encrypt-file-alist.
I don't understand. Is this encryption stuff not hooked into Gnus in
any way? That might explain my experience with it so far.
I encrypted my .authinfo file using gnus-encrypt-write-file-contents
(gpg, AES), but when I then fire up Gnus I don't get prompted for a
password, and Gnus can't read the file.
I used the Customize interface to add an entry to
gnus-encrypt-file-alist, which wound up looking like this:
(("/home/sharris/.authinfo" (gpg "AES")))
Note that the gpg and cipher specification are in a nested list, which
differs from the example alist:
'(("/home/tzz/alpha" gpg "AES") ; GPG on single file
;; xor encryption on all files matching "beta"
("beta" gnus-encrypt-xor "Semi-Secret"))
I tried redefining gnus-encrypt-file-alist like so
(("/home/sharris/.authinfo" gpg "AES"))
but Gnus still fails to take notice of 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.
I can certainly help to test it.
--
Steven E. Harris
next prev parent reply other threads:[~2004-07-23 21:39 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
2004-07-23 17:16 ` Steven E. Harris
2004-07-23 17:00 ` Ted Zlatanov
2004-07-23 21:39 ` Steven E. Harris [this message]
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=jk4iscecsj7.fsf@W003275.na.alarismed.com \
--to=seh@panix.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).