Re: Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Tobias Leupold via Gnupg-users
Hi Vincent! Thanks a lot for this insight! When it comes to encryption, I would consider myself a "power user", but still a user. I never heard of all this until now. What I, from the perspective of an end-user, saw was: I generate a new key. And then: "Pass no work on me phone anymore, OpenK

Re: Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Vincent Breitmoser via Gnupg-users
Hey list, OpenKeychain maintainer here. As Werner chose to omit some details here that seem pertinent, I will add: No, it is not because you are delaying the deployment of new and a much faster algorithm mode. The packet format referred to here is GnuPG-specific. In November 2023, GnuPG fo

Re: Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Vincent Breitmoser via Gnupg-users
Hey Bruce, On 04.03.24 21:53, Bruce Walzer wrote: * https://articles.59.ca/doku.php?id=pgpfan:noae_shame There is more if you search for it: https://kagi.com/search?q=gpg+%22packet+type+20%22&r=no_region&sh=HeSUA3hoI5SeCuA2TTrNig Cheers - V ___

Re: Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Tobias Leupold via Gnupg-users
> Ah... That question leads to an awkward discussion these days. There > was a IETF standards process that led to the OCB mode now supported by > GnuPG and others. GnuPG (and others) implemented it before the new > standard was officially released (there seemed to be consensus). That > standards pr

Re: Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Bruce Walzer
On Mon, Mar 04, 2024 at 12:03:41PM +0100, Tobias Leupold via Gnupg-users wrote: [...] > After some research, I found > > https://github.com/open-keychain/open-keychain/issues/2886 , > > describing this exact issue. That would be the cipher block mode proliferation issue. > As a possible fix

Re: Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Tobias Leupold via Gnupg-users
Hi Werner, thanks for the clarification! > All the major implementers (Ribose RNP, GnuPG, BouncyCastle, OpenPGP.js) > took great care to first deploy the software with support for the new > mode before actually creating keys with a preference for that mode [1]. > Unfortunately a small group of pe

Re: [gpg-agent] Empty OPTION xauthority=

2024-03-04 Thread Matěj Cepl
On Mon Mar 4, 2024 at 9:13 AM CET, Werner Koch wrote: > Because all components of gnupg will start gpg-agent and the other > daemons oin the fly and make sure that only one is started. Do I understand it correctly that gnupg contains smaller version of systemd (dependency activation) inside of its

Re: Your message to Gnupg-users awaits moderator approval

2024-03-04 Thread Matěj Cepl
On Mon Mar 4, 2024 at 2:19 PM CET, gnupg-users-owner wrote: > Your mail to 'Gnupg-users' with the subject > > Re: [gpg-agent] Empty OPTION xauthority= > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Message body is too big: 63276 b

Re: [gpg-agent] Empty OPTION xauthority=

2024-03-04 Thread Werner Koch via Gnupg-users
On Mon, 4 Mar 2024 14:19, Matěj Cepl said: > Do I understand it correctly that gnupg contains smaller version > of systemd (dependency activation) inside of itself and that No. It is not required. Just don't let systemd start gpg-agent or dirmngr with option --supervised. If you use ssh just m

Re: Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Werner Koch via Gnupg-users
On Mon, 4 Mar 2024 12:03, Tobias Leupold said: > So: Is it wise and/or necessary to disable that for new GnuPG generated keys, > for the sake of interoperability? Or will the others catch up and implement No, it is not because you are delaying the deployment of new and a much faster algorithm

Re: No secret key

2024-03-04 Thread Eva Bolten via Gnupg-users
Hi, First of all: The usual procedure when asking for advice is to tell us which gpg version you are using. And on which operation system. But it seems likely that in this case the info is not necessary. > I received this message when using --clear-sign. > gpg: no default secret key: No secret

Should one really disable AEAD for recent GnuPG created PGP keys?

2024-03-04 Thread Tobias Leupold via Gnupg-users
Hi all :-) Apparently, there are some problems with the new defaults that are set when one creates a PGP key using a recent version of GnuPG (2.4). I ran into this after generating a new ECC/ED25519 key to replace my "old" RSA one. The problem showed up when I re-encrypted my pass password stor

No secret key

2024-03-04 Thread Richard Bostrom via Gnupg-users
Sirs and ladie! I received this message when using --clear-sign. gpg: no default secret key: No secret key gpg: clear-sign dialed: No secret key Both my public and private key has been imported. The key was made with a different user (as sudo)The current user is a non-sudo user. Yours truly Ric

Re: [gpg-agent] Empty OPTION xauthority=

2024-03-04 Thread Werner Koch via Gnupg-users
On Sun, 3 Mar 2024 20:38, Matěj Cepl said: > 1. Could you please explain why it is racy? Why from all services Because all components of gnupg will start gpg-agent and the other daemons oin the fly and make sure that only one is started. Systemd does not know about this specific start mechanism