From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: silipwn <mail@silipwn.digital>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-encrypt-entry fails [9.4 (nil @ /home/silipwn/.emacs.d/.local/straight/build/org-mode/)]
Date: Fri, 15 May 2020 21:17:57 +0200 [thread overview]
Message-ID: <87k11dxb16.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20200515164629.rz7rsxomlaxqyeu3@evangelion> (silipwn's message of "Fri, 15 May 2020 22:16:29 +0530")
silipwn <mail@silipwn.digital> writes:
> The current commit, still results in a error. I had a set the
> org-crypt-key to nil.
This is not a valid value: `org-crypt-key' must be a string.
> It still prompts to use a key.
I think setting `org-crypt-key' to nil means: use all keys in your key
ring. Some of them are not trusted, others may be invalid. Again, use
default empty string if you don't want to set a key and would rather use
symmetric encryption.
> The current backtrace is similar to this:
>
> Debugger entered--Lisp error: (error "GPG error: \"Encrypt failed\",
> \"Unusable public key: 49F84EA6007F964D; Exit\"")
> signal(error ("GPG error: \"Encrypt failed\", \"Unusable public key:
> 49F84EA6007F964D; Exit\""))
> error("GPG error: \"Encrypt failed\", \"Unusable public key:
> 49F84EA6007F964D; Exit\"")
You should check that key in your key ring. It probably has expired and
cannot be used for encryption.
Regards,
next prev parent reply other threads:[~2020-05-15 19:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 2:56 Bug: org-encrypt-entry fails [9.4 (nil @ /home/silipwn/.emacs.d/.local/straight/build/org-mode/)] silipwn
2020-05-15 15:00 ` Nicolas Goaziou
2020-05-15 16:46 ` silipwn
2020-05-15 19:17 ` Nicolas Goaziou [this message]
2020-05-16 3:31 ` [Solved]: " silipwn
2020-05-18 13:46 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k11dxb16.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@silipwn.digital \
/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/org-mode.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).