From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Brady Trainor <algebrat@uw.edu>
Cc: info-gnus-english@gnu.org
Subject: Re: Prevent "save to ~/.authinfo[Y/y/N/n]" prompt
Date: Tue, 30 Sep 2014 01:59:42 +0100 [thread overview]
Message-ID: <87egutzzwh.fsf@skimble.plus.com> (raw)
In-Reply-To: <87r3yumac3.fsf@uw.edu> (Brady Trainor's message of "Mon, 29 Sep 2014 13:38:04 -0700")
[-- Attachment #1.1: Type: text/plain, Size: 1048 bytes --]
Brady Trainor <algebrat@uw.edu> writes:
> Hi, something is wrong with my gpg use, so until I fix it, I will just
> enter my password for each use. (I will likely start a new thread about
> my gpg soon.)
>
> But something I never really liked, is the prompt when doing so to save
> this information in `~/.authinfo'.
>
> Is there a way to prevent this prompt. I think it'd be nice for initial
> setup of Gnus as well, as storing passwords (securely) may not be the
> first thing you get around to, and one may get nervous about accidently
> saving it in this plain text file.
Hi Brady.
I have *never* seen this behaviour, so maybe it is some slight quirk at
your end which is causing it? Perhaps the way that something is
saved/configured in your gpg setup? But whatever is causing it, it is
definitely non-standard behaviour!
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, fluxbox 1.3.5, emacs 24.3.93.1
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-09-30 0:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 20:38 Brady Trainor
2014-09-30 0:59 ` Sharon Kimble [this message]
2014-09-30 2:25 ` Brady Trainor
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=87egutzzwh.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=algebrat@uw.edu \
--cc=info-gnus-english@gnu.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).