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
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,
Sorry for asking another thing about this. For sure, I didn't want to set off
an avalanche, and I still don't want to. But from a user's perspective, this
is simply very confusing and also unsettling.
I think that somewhere, there should be some documentation, FAQ or whatever,
as a definitive
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
> 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
