Page MenuHome GnuPG
Feed Advanced Search

Jan 27 2024

stardiviner added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

I upgraded to gnupg 1.4.4 now, the problem is gone. Thanks for working.

Jan 27 2024, 5:09 AM · Emacs, gnupg, Bug Report

Jan 26 2024

fgunbin added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Thanks @gniibe and everybody!

Jan 26 2024, 5:32 PM · Emacs, gnupg, Bug Report
gniibe closed T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG) as Resolved.

Fixed in GnuPG 2.4.4.

Jan 26 2024, 1:11 AM · Emacs, gnupg, Bug Report

Jan 23 2024

juergenhoetzel added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Arch Linux: https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg
FreeBSD: https://cgit.freebsd.org/ports/tree/security/gnupg

I don't see the patch is applied. Please wait for GnuPG release 2.4.4.

Jan 23 2024, 12:36 PM · Emacs, gnupg, Bug Report
ikloecker added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Indeed, openSUSE has applied the patch: https://build.opensuse.org/package/show/openSUSE%3AFactory/gpg2

Jan 23 2024, 8:18 AM · Emacs, gnupg, Bug Report
gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Arch Linux: https://gitlab.archlinux.org/archlinux/packaging/packages/gnupg
FreeBSD: https://cgit.freebsd.org/ports/tree/security/gnupg

Jan 23 2024, 1:05 AM · Emacs, gnupg, Bug Report

Jan 22 2024

ikloecker added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Works as expected on openSUSE Tumbleweed with gpg2-2.4.3-4.2.x86_64:

$ gpg2 --version
gpg (GnuPG) 2.4.3
libgcrypt 1.10.3
[...]
Jan 22 2024, 10:02 PM · Emacs, gnupg, Bug Report
juergenhoetzel added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

i still observe the same behavior:

What do you mean? I can't replicate the behavior described by you, using the GnuPG from the repo, or the one of Debian 2.4.3-2.

Jan 22 2024, 6:04 PM · Emacs, gnupg, Bug Report
gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

i still observe the same behavior:

Jan 22 2024, 5:57 AM · Emacs, gnupg, Bug Report

Jan 21 2024

juergenhoetzel added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

For a while, distributions can apply rG2f872fa68c65 for 2.4 series.

Jan 21 2024, 7:59 PM · Emacs, gnupg, Bug Report

Dec 27 2023

gniibe triaged T6909: pinentry: Drop pinentry-emacs support as Normal priority.
Dec 27 2023, 4:01 AM · Feature Request, pinentry, Emacs

Nov 17 2023

gniibe changed the status of T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG) from Open to Testing.

Applied to 2.4, too.

Nov 17 2023, 12:57 AM · Emacs, gnupg, Bug Report

Sep 6 2023

werner added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

ack

Sep 6 2023, 8:00 PM · Emacs, gnupg, Bug Report
DamienCassou added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

@werner: What do you mean by "We have a fix for now"? Are you referring to @gniibe's patch?

Sep 6 2023, 2:44 PM · Emacs, gnupg, Bug Report
werner lowered the priority of T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG) from High to Low.

We have a fix for now and thus I lower the priority. Given that EasyPG mimics the GPGME API we should here also use another pipe to convey the passphrase (e.g. for symmetric encryption).

Sep 6 2023, 2:32 PM · Emacs, gnupg, Bug Report

Jun 12 2023

werner added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

I consider the entire idea of receiving a passphrase and data on the same channel to be a bad for security and robust coding. The whole thing is a historical oddity which we kept for the sake of mutt(1)'s legacy way of invoking pgp. Thus I won't consider 3) the best option.

Jun 12 2023, 8:22 AM · Emacs, gnupg, Bug Report
gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

To summarize, here is the situation:

  • Ideally, it would be good to modify GnuPG and Emacs EasyPG to implement status handling and input handling in better way.
Jun 12 2023, 2:13 AM · Emacs, gnupg, Bug Report

Jun 10 2023

thesamesam added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Ah, I see https://dev.gnupg.org/rG2f872fa68c6576724b9dabee9fb0844266f55d0d applies cleanly. I guess can go with that, although would prefer it if on the 2.4 branch.

Jun 10 2023, 11:00 PM · Emacs, gnupg, Bug Report
thesamesam added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Is there a commit we could backport downstream to 2.4.x? We've had quite a few reports of this.

Jun 10 2023, 10:56 PM · Emacs, gnupg, Bug Report

May 24 2023

gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

I pushed the change which keeps old status report behavior to master.
Let me test the change.

May 24 2023, 3:48 AM · Emacs, gnupg, Bug Report
gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

looks simpler to me.

May 24 2023, 3:24 AM · Emacs, gnupg, Bug Report

May 23 2023

werner added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Hmm, for the latter this:

May 23 2023, 3:03 PM · Emacs, gnupg, Bug Report
gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Orthogonally, here is possible change for GnuPG, if we need to support the workaround of compress-level 0 in ~/.gnupg/gpg.conf.

May 23 2023, 2:11 PM · Emacs, gnupg, Bug Report
gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

OK, here is my changes which always use make-temp-file (to avoid confusion between data input and passphrase input).

May 23 2023, 10:47 AM · Emacs, gnupg, Bug Report
gniibe claimed T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

I use epg.el with the change of removing the wait:

May 23 2023, 9:23 AM · Emacs, gnupg, Bug Report

May 8 2023

fgunbin added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

@werner We could make the wait conditional on (equal epg-gpg-program "gpg"), that is, only when user has GnuPG 1.x.

May 8 2023, 4:54 PM · Emacs, gnupg, Bug Report
werner added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

Well okay, then I have no workaround. However, I won't consider this a bug because BEGIN_ENCRYPTION marks the start of the actual encryption process but not when it starts to read input data.

May 8 2023, 12:53 PM · Emacs, gnupg, Bug Report
gniibe added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

The change rG60963d98cfd8: gpg: Detect already compressed data also when using a pipe. for T6332 introduce IOBUF_IOCTL_PEEK.

May 8 2023, 11:10 AM · Emacs, gnupg, Bug Report

May 7 2023

stardiviner added a comment to T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG).

@werner I tested by switch back to GnuPG 2.4.1 (I downgraded to 2.4.0 before to temporary work around issue), adding compress-level 0 to gpg.conf file. It's not working. The problem still exist.

May 7 2023, 5:09 PM · Emacs, gnupg, Bug Report

May 5 2023

werner triaged T6481: BEGIN_ENCRYPTION status output happens later in 2.4.1 (breaks Emacs's EasyPG) as High priority.

I have not yet experienced that although I am using Gnus with encrypted mail all the time. My guess is that this is due to the improved compressed input detection in gpg. You might be able to work around it by adding compress-level 0 to gpg.conf

May 5 2023, 7:35 PM · Emacs, gnupg, Bug Report

Sep 26 2022

gniibe added a comment to T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).

pinentry-emacs is obsolete. It's for older Emacs (<= 25, IIUC) which had lisp/pinentry.el.
For Emacs 26 and newer, you can simply use epa-pinentry-mode having the value of loopback.

Sep 26 2022, 8:11 AM · Feature Request, pinentry, Emacs

Aug 25 2022

thesamesam added a comment to T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).

That's a fair point, cheers!

Aug 25 2022, 9:49 AM · Feature Request, pinentry, Emacs
werner triaged T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR) as Normal priority.

Let's turn this into a feature request.

Aug 25 2022, 9:16 AM · Feature Request, pinentry, Emacs
thesamesam updated the task description for T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:54 AM · Feature Request, pinentry, Emacs
thesamesam changed External Link from https://bugs.gentoo.org/794649 to https://debbugs.gnu.org/33847 on T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:54 AM · Feature Request, pinentry, Emacs
thesamesam changed External Link from https://bugs.gentoo.org/794649) to https://bugs.gentoo.org/794649 on T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:53 AM · Feature Request, pinentry, Emacs
thesamesam set External Link to https://bugs.gentoo.org/794649) on T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:53 AM · Feature Request, pinentry, Emacs
thesamesam created T6160: pinentry Emacs support assumes socket location at ${TMPDIR}/emacs${UID}, fails to connect (need to respect XDG_RUNTIME_DIR).
Aug 25 2022, 8:53 AM · Feature Request, pinentry, Emacs

Jun 4 2019

maiden_taiwan closed T4542: gpg-agent loses characters when prompting for a GPG passphrase over SSH in Emacs as Resolved.

No worries -- you led me in the direction of a solution when you mentioned loopback mode. I appreciate your time and your help!

Jun 4 2019, 2:34 AM · Emacs, Documentation, pinentry, Bug Report
gniibe added projects to T4542: gpg-agent loses characters when prompting for a GPG passphrase over SSH in Emacs: Documentation, Emacs.

Sorry, I responded in a mode of "tracking a bug to fix soonish". I should have changed my mode into showing HOWTO.
Thanks for sharing useful link.

Jun 4 2019, 2:07 AM · Emacs, Documentation, pinentry, Bug Report
gniibe added a member for Emacs: gniibe.
Jun 4 2019, 2:03 AM
gniibe set the color for Emacs to Checkered.
Jun 4 2019, 2:03 AM