Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement specification changes from draft-ietf-openpgp-crypto-refresh #1442

Open
13 of 15 tasks
larabr opened this issue Nov 17, 2021 · 0 comments
Open
13 of 15 tasks

Implement specification changes from draft-ietf-openpgp-crypto-refresh #1442

larabr opened this issue Nov 17, 2021 · 0 comments
Labels
Milestone

Comments

@larabr
Copy link
Collaborator

larabr commented Nov 17, 2021

The crypto-refresh document is still being drafted (https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/), but we should implement/update the new features before its release.

To update/change:

  • AEAD encrypted messages
  • AEAD encrypted secret keys (S2K identifier 253)
  • V6 secret keys
  • V6 signatures
  • V6 PKESK and SKESK
  • support keys with no User IDs
  • use direct-key signatures for reading and writing key expiration, algorithm preferences, etc
  • drop support for armoring "multipart" messages
  • don't create armor checksum lines
  • padding packet
  • intended recipient fingerprint (not really new but encouraged by the crypto refresh)
  • packet criticality and error handling
  • reject invalid MPIs
    ...

To add from scratch:

  • Curve448
  • Argon2
    ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant