Closed dkg closed 1 year ago
Thanks for pointing this out, v2 is still work in progress. I will address the issue with the profile names in the next iteration.
Fixed with commit 8617aeb9 on the gosop-gopenpgp-v3
branch
Outputs now:
./gosop list-profiles encrypt
rfc4880: CFB (SEIPDv1)
draft-koch-eddsa-for-openpgp-00: AEAD (SEIPDv2) enabled
draft-ietf-openpgp-crypto-refresh-10: AEAD (SEIPDv2) enabled
./gosop list-profiles generate-key
rfc4880: generates 3072-bit rsa keys
draft-koch-eddsa-for-openpgp-00: generates EdDSA/ECDH v4 keys with Curve25519
draft-ietf-openpgp-crypto-refresh-10: generates Ed25519/X25519 v6 keys with Curve25519
Thanks for all the work on gosop recently!
I note from the interop test suite gosop v2 implements three different profiles for both encrypt and generate-key. Two of the profile names are not compliant with the sop specification because they do not identify specific individual drafts. The extended version information for this instance of gosop is:
It says:
Profiles for the encrypt subcommand:
rfc4880
draft-koch-openpgp
draft-ietf-openpgp-crypto-refresh
Profiles for the generate-key subcommand
draft-koch-openpgp
draft-ietf-openpgp-crypto-refresh
rfc4880
In particular,
draft-koch-openpgp
anddraft-ietf-openpgp-crypto-refresh
are not full names of drafts. Neither includes the specific draft version number, anddraft-koch-openpgp
itself is ambiguous. For example,draft-ietf-openpgp-crypto-refresh-08
would produce different data fromsop encrypt
than woulddraft-ietf-openpgp-crypto-refresh-09
due to the inclusion of a size field in PKESKv6 between those versions. Even worse,draft-koch-openpgp
doesn't refer to any single specification, let alone version number, as there are three distinct I-D's with that prefix.Please use specific draft versions if you're targeting a draft. If you think there are no functional difference between subsequent versions of the same draft, please use the higher draft version number that the implementation aims to be compliant with.