unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: John Williams <johnfrombluff@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 29907@debbugs.gnu.org
Subject: bug#29907: 25.3; Easy PG should warn users that passphrases are not cached forever
Date: Sun, 28 Jan 2018 18:31:28 +0000	[thread overview]
Message-ID: <CAG_41YJj0gjLHK0cop6Pf8LJMn2qVCqWoparOqrQ9m3M32OTbQ@mail.gmail.com> (raw)
In-Reply-To: <87mv0ykkue.fsf@users.sourceforge.net>

[-- Attachment #1: Type: text/plain, Size: 2545 bytes --]

Thanks!

On Mon, 29 Jan 2018 at 05:29 Noam Postavsky <npostavs@users.sourceforge.net>
wrote:

> John Williams <johnfrombluff@gmail.com> writes:
>
> > I encrypted a file using Easy PG. When I did so, I specified a pass
> > phrase via a window manager pop-up dialog and checked the option to
> > save the pass phrase in the "keyring". I am using GNOME, so I assumed
> > that the "keyring" in question was Seahorse.
> >
> > I opened the file again and was not prompted for the pass phrase. I
> > was happy. I rebooted to see if the cache was ephemeral, and lo, it
> > was not. I was happy.
> >
> > A few days later, I attempted to open the file again, and was prompted
> > for the password. I had forgotten it, and now there is no way to
> > access the contents of the file. I am very sad, because the contents
> > of the file are worth about $20,000 to me.
>
> Hmm, I don't think gpg-agent caches over reboots, so I wonder what saved
> your pass phrase the first time.
>
> > Mea culpa. I should not have trusted software for such an important
> > task without reading the manual. But after reading the manual, I find
> > no mention that the pass phrase caching is ephemeral. After much
> > Googling, I found out about gpg-agent and max-cache-ttl.
> >
> > I don't think it's reasonable to expect users to read long manuals, or
> > already be experts in underlying technology, in order to use simple
> > functionality. I also think the the dialog that prompts for a pass
> > phrase should inform the user about default-cache-ttl and
> > max-cache-ttl.
> >
> > I also think the dialog, and the manual, should emphasise very
> > strongly that pass phrases are not cached forever.
>
> I somewhat feel that the term "cache" already implies temporary, but
> saying it explicitly shouldn't hurt I guess.  Emacs is not in control of
> the dialog at all, so we cannot affect that.
>
> --- i/doc/misc/epa.texi
> +++ w/doc/misc/epa.texi
> @@ -474,7 +474,9 @@ Caching Passphrases
>
>  Typing passphrases is a troublesome task if you frequently open and
>  close the same file.  GnuPG and EasyPG Assistant provide mechanisms to
> -remember your passphrases.  However, the configuration is a bit
> +remember your passphrases for a limited time.  Using these, you only
> +need to re-enter the passphrase occasionally.
> +However, the configuration is a bit
>  confusing since it depends on your GnuPG installation@xref{GnuPG
>  version compatibility}, encryption method (symmetric or public key),
>  and whether or not you want to use gpg-agent.  Here are some
>

[-- Attachment #2: Type: text/html, Size: 3154 bytes --]

  reply	other threads:[~2018-01-28 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-30  2:18 bug#29907: 25.3; Easy PG should warn users that passphrases are not cached forever John Williams
2018-01-28 16:29 ` Noam Postavsky
2018-01-28 18:31   ` John Williams [this message]
2018-01-31  3:36     ` Noam Postavsky

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=CAG_41YJj0gjLHK0cop6Pf8LJMn2qVCqWoparOqrQ9m3M32OTbQ@mail.gmail.com \
    --to=johnfrombluff@gmail.com \
    --cc=29907@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).