unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Rohleder <mike@rohleder.de>
To: Leo Famulari <leo@famulari.name>
Cc: 52483@debbugs.gnu.org
Subject: bug#52483: GnuPG 2.2.30 cannot do symmetric encryption
Date: Sun, 19 Dec 2021 02:32:47 +0100	[thread overview]
Message-ID: <875yrlbcqo.fsf@rohleder.de> (raw)
In-Reply-To: <YbjKVHCCHa8OvKqS@jasmine.lan> (Leo Famulari's message of "Tue, 14 Dec 2021 11:46:12 -0500")

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

Leo Famulari <leo@famulari.name> writes:
> If emacs-pinentry cannot use a current GnuPG, what should we do? And
> maybe we don't need emacs-pinentry anymore?:
>
> https://emacs.stackexchange.com/a/64721
>

I don't think emacs-pinentry is needed, because adding
"allow-emacs-pinentry" to gpg-agent.conf worked (for me) (at least)
since several years in (guix) emacs w/o using emacs-pinentry (or other
emacs customization).

---
Wir kommen nackt auf diese Welt und atmen ein.
Wir atmen aus und verlassen diese Welt mit leeren Händen.
und dazwischen gestalten wir unser Leben.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]

      parent reply	other threads:[~2021-12-19  1:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 16:46 bug#52483: GnuPG 2.2.30 cannot do symmetric encryption Leo Famulari
2021-12-14 17:32 ` Leo Famulari
2021-12-14 17:33 ` bug#52483: [PATCH v2] gnu: GnuPG: Update gnupg-2.2.32 to 2.2.33 Leo Famulari
2021-12-17 17:32   ` Leo Famulari
2021-12-18  4:56     ` bug#52483: GnuPG 2.2.30 cannot do symmetric encryption Maxim Cournoyer
2021-12-18 23:53       ` Leo Famulari
2021-12-19 20:25         ` Maxim Cournoyer
2021-12-19 20:33           ` Leo Famulari
2021-12-19 20:36           ` Leo Famulari
2021-12-23  0:01             ` Leo Famulari
2021-12-26 22:46             ` Leo Famulari
2021-12-19  1:32 ` Michael Rohleder [this message]

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yrlbcqo.fsf@rohleder.de \
    --to=mike@rohleder.de \
    --cc=52483@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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/guix.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).