From: "Steven E. Harris" <seh@panix.com>
Subject: Re: authinfo/netrc file encryption status -- GnuPG
Date: Wed, 04 Aug 2004 15:55:34 -0700 [thread overview]
Message-ID: <jk4oelqy0m1.fsf@W003275.na.alarismed.com> (raw)
In-Reply-To: <4noelsxi20.fsf@lifelogs.com> (Ted Zlatanov's message of "3 Aug 2004 13:11:51 -0400")
"Ted Zlatanov" <tzz@lifelogs.com> writes:
> I tested them, let me know if you get good results too.
More feedback after using the updates for most of the day: I now need
to type my .authinfo decryption password more often than I used to
have to type the individual server passwords.
I have gnus-encrypt-password-cache-expiry set to 600, or ten
minutes. Now, whenever I contact a server that I haven't exchanged
data with for ten minutes, Gnus prompts me for my decryption
password. Without an encrypted .authinfo -- one missing the password
specifications to begin with -- Gnus will only prompt me for a
password if the server has disconnected, and even then Gnus still
seems to cache the passwords until I close a server manually.
The distinction here is that with an encrypted .authinfo, expiration
of the password cache seems to cause Gnus to think that it needs to
re-authenticate, even if it's not necessary with an .authinfo missing
passwords altogether.
Of course my descriptions involve a lot of hand-waving because I don't
know how Gnus actually handles server disconnects and authentication
requests. I'm just comparing against the "normal" behavior I've grown
accustomed to over the last few years.
Summarizing: With no passwords in a non-encrypted .authinfo file, I
type a password for each server each time I start Gnus, and I usually
don't have to repeat that password until I exit and restart Gnus. With
passwords in an encrypted .authinfo file, I have to type the
decryption password every gnus-encrypt-password-cache-expiry period.
Is that the expected behavior?
--
Steven E. Harris
next prev parent reply other threads:[~2004-08-04 22:55 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
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 ` Steven E. Harris [this message]
2004-08-06 17:31 ` authinfo/netrc file encryption status -- GnuPG 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=jk4oelqy0m1.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).