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.

Sign up for GitHub

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

Jump to bottom

No CRC24 Checksum for v6 #24

Open
TJ-91 opened this issue Apr 26, 2023 · 3 comments
Open

No CRC24 Checksum for v6 #24

TJ-91 opened this issue Apr 26, 2023 · 3 comments
Assignees
@TJ-91
Labels
v6 req. deferred to upstream A requirement for v6 which we don't implement and which we need to inform the upstream project about

Comments

@TJ-91
Copy link
Collaborator

TJ-91 commented Apr 26, 2023

https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-crypto-refresh-08#name-optional-checksum

  • An ASCII-armored Encrypted Message packet sequence that ends in an v2 SEIPD packet MUST NOT contain a CRC24 footer.
  • An ASCII-armored sequence of Signature packets that only includes v6 Signature packets MUST NOT contain a CRC24 footer.
  • An ASCII-armored Transferable Public Key packet sequence of a v6 key MUST NOT contain a CRC24 footer.
  • An ASCII-armored keyring consisting of only v6 keys MUST NOT contain a CRC24 footer.
@TJ-91 TJ-91 self-assigned this Apr 26, 2023
@TJ-91 TJ-91 mentioned this issue Apr 26, 2023
Closed
@falko-strenzke
Copy link
Contributor

@TJ-91 I this still open?

@TJ-91
Copy link
Collaborator Author

TJ-91 commented Feb 5, 2024

Yes the armoring is still not updated

@falko-strenzke
Copy link
Contributor

OK, for all the remaining open issues we should also as the upstream project how/where we should document them for them. We'll leave this open for now.

@falko-strenzke falko-strenzke added the v6 req. deferred to upstream A requirement for v6 which we don't implement and which we need to inform the upstream project about label Feb 5, 2024
@TJ-91 TJ-91 mentioned this issue Mar 22, 2024
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TJ-91 TJ-91

Labels
v6 req. deferred to upstream A requirement for v6 which we don't implement and which we need to inform the upstream project about
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TJ-91 @falko-strenzke