From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: url-auth-tests hang if authinfo is encrypted
Date: Tue, 04 Apr 2017 10:53:21 -0400 [thread overview]
Message-ID: <87k2702pi6.fsf@lifelogs.com> (raw)
In-Reply-To: 877f311enn.fsf@yandex.com
On Mon, 03 Apr 2017 20:20:44 +0100 Colin Baxter <m43cap@yandex.com> wrote:
CB> My ~/.authinfo is encrypted to ~/.authinfo.gpg; consequently,
CB> url-auth-tests hangs, waiting for a password that never comes. If I
CB> decrypt the file to ~/.authinfo then the test succeeds.
CB> Is there anyway the test could be made to prompt the user to enter the
CB> password? Failing that then perhaps the test ought to fail cleanly when
CB> ~/.authinfo.gpg is found.
CB> Encrypting the ~/.authinfo is quite common, I believe.
I think the user's personal setup shouldn't affect the tests.
The solution can be either automatic (auth-source knows it's inside a
test, or EPG doesn't try to decrypt in a test environment) or explicit
(tests override `auth-sources' and/or EPG). For the automatic
option, I can add the code to auth-source if anyone can suggest how to
tell it's inside a test environment.
Maybe others can think of other options?
Ted
next prev parent reply other threads:[~2017-04-04 14:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 19:20 url-auth-tests hang if authinfo is encrypted Colin Baxter
2017-04-03 19:40 ` Eli Zaretskii
2017-04-04 6:15 ` Colin Baxter
2017-04-04 14:14 ` Eli Zaretskii
2017-04-15 9:12 ` [PATCH] Fix potentially hanging url-auth tests Jarno Malmari
2017-04-15 15:36 ` Colin Baxter
2017-04-16 11:21 ` Jarno Malmari
2017-04-04 14:53 ` Ted Zlatanov [this message]
2017-04-04 16:04 ` url-auth-tests hang if authinfo is encrypted Andreas Schwab
2017-04-04 20:03 ` Colin Baxter
2017-04-05 6:43 ` Colin Baxter
2017-04-05 13:33 ` Ted Zlatanov
2017-04-06 19:29 ` Jarno Malmari
2017-04-07 7:22 ` Colin Baxter
2017-04-07 7:37 ` Eli Zaretskii
2017-04-07 13:34 ` Colin Baxter
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2702pi6.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).