emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Karl Voit <news2042@Karl-Voit.at>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-crypt fails if default key is expired while non-default key is to be used
Date: Mon, 23 Jan 2023 10:16:02 +0000	[thread overview]
Message-ID: <875ycx7dzx.fsf@localhost> (raw)
In-Reply-To: <2023-01-22T18-32-17@devnull.Karl-Voit.at>

Karl Voit <devnull@Karl-Voit.at> writes:

> When I invoked org-decrypt-entry, decrypting works like always. Then
> I modified something in this heading which is tagged with :crypt:.
> On saving that buffer, org-crypt issues an error message:
> | Error: (error "GPG error: \"Encrypt failed\", \"Unusable public key:
> | A1234567; Exit\"")
> This A1234567 key is my default key and not the org-openpgp-key.
> org-encrypt-entry is causing this error at:
> |	;; Text and key have to be identical, otherwise we
> |	;; re-crypt.
> |	(if (and (equal crypt-key key)
> |		 (string= checksum (sha1 contents)))
> |	    (get-text-property 0 'org-crypt-text contents)
> |	  (epg-encrypt-string epg-context contents crypt-key)))
> After fixing the expiry date of A1234567, org-crypt was working
> properly, using the correct org-openpgp-key again.
> I do think this is wrong behavior: when the default key is expired
> but a specific secondary key is used, encryption should be possible.

All we do here is calling `epg-encrypt-string' with crypt key obtained
using `org-crypt-key-for-heading', which see.

May I know how exactly did you set `org-crypt-key'? Do you happen to
have CRYPTKEY properties somewhere in your buffer?

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  reply	other threads:[~2023-01-23 10:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 17:41 org-crypt fails if default key is expired while non-default key is to be used Karl Voit
2023-01-23 10:16 ` Ihor Radchenko [this message]
2023-01-23 14:58   ` Karl Voit
2023-01-24  9:14     ` Ihor Radchenko
2023-01-29 17:37       ` Karl Voit
2023-01-30 13:53         ` Ihor Radchenko
2023-01-30 22:00           ` Karl Voit
2023-01-31 10:32             ` Ihor Radchenko
2023-04-18 13:28               ` Karl Voit

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:

  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=875ycx7dzx.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=news2042@Karl-Voit.at \


* 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


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).