unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daiki Ueno <ueno@unixuser.org>
Cc: 12923@debbugs.gnu.org, Oleksandr Gavenko <gavenkoa@gmail.com>
Subject: bug#12923: 24.2; epa-file--find-file-not-found-function: Opening input file: Can't decrypt, Exit
Date: Wed, 21 Nov 2012 09:00:58 -0500	[thread overview]
Message-ID: <jwvwqxfjbwp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87lidw54hx.fsf-ueno@unixuser.org> (Daiki Ueno's message of "Wed,  21 Nov 2012 06:49:46 +0900")

> If the above magic works well for typical use-cases, it might be worth
> adding them to Emacs too.

I took this bug-report to say "make sure that we handle .gpg files in
a file-safe way, showing the raw-bytes if we can't show the decrypted
content".  So rather than try to detect that we have a keyring, we
should just try to decrypt and look at the resulting error
(which should hopefully be different for "bad decryption key" than it
is for "trying to decrypt something else (e.g. a keyring file)").


        Stefan





  parent reply	other threads:[~2012-11-21 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 13:42 bug#12923: 24.2; epa-file--find-file-not-found-function: Opening input file: Can't decrypt, Exit Oleksandr Gavenko
2012-11-20  7:32 ` Daiki Ueno
2012-11-20 18:11   ` Oleksandr Gavenko
2012-11-20 21:49     ` Daiki Ueno
2012-11-21  1:12       ` Daiki Ueno
2012-11-21 14:00       ` Stefan Monnier [this message]
2021-12-04  4:39         ` Lars Ingebrigtsen

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=jwvwqxfjbwp.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=12923@debbugs.gnu.org \
    --cc=gavenkoa@gmail.com \
    --cc=ueno@unixuser.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).