Skip to content

Dc v6 patch3 #2371

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

Merged
merged 12 commits into from
Nov 19, 2024
Merged

Dc v6 patch3 #2371

Changes from 1 commit
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
903f618
Added content for #2314
danielcuthbert Nov 11, 2024
ed62e2a
typo in rfc
danielcuthbert Nov 11, 2024
30d6e32
removed cto ref
danielcuthbert Nov 12, 2024
abff3c7
amdned 6.9.1 to be more reflective of PQC status quo
danielcuthbert Nov 12, 2024
4485d7e
fixed linting issues
danielcuthbert Nov 13, 2024
9860e9c
tag fixes
elarlang Nov 13, 2024
26d5b8b
addressing PR comments
danielcuthbert Nov 14, 2024
169cb12
added keywrapping explanation to appendix
danielcuthbert Nov 18, 2024
feddb50
added NIST PQC FIPS guidelines to appendix
danielcuthbert Nov 18, 2024
be79516
ficed 6.6.5 to read more clearly
danielcuthbert Nov 19, 2024
58446f4
Minor tweak
tghosth Nov 19, 2024
3d0d929
linting
tghosth Nov 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions 5.0/en/0x97-Appendix-V_Cryptography.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -292,3 +292,7 @@ The following KDFs are explicitly banned and MUST NOT be used due to insufficien
| -------------- | ---------------------------------------------------------------------------------- |
| MD5-based KDFs | [RFC 1321](https://www.rfc-editor.org/info/rfc1321) |
| SHA-1-based KDFs | [RFC 3174](https://www.rfc-editor.org/info/rfc3174) & [RFC 6194](https://www.rfc-editor.org/info/rfc6194) |

### Post-Quantum Encryption Standards

PQC implementations must be inline with [FIPS-203](https://csrc.nist.gov/pubs/fips/203/ipd)/[204](https://csrc.nist.gov/pubs/fips/204/ipd)/[205](https://csrc.nist.gov/pubs/fips/205/ipd) as there isn't any hardened code nor implementation reference yet. https://www.nist.gov/news-events/news/2024/08/nist-releases-first-3-finalized-post-quantum-encryption-standards
Copy link
Collaborator

@randomstuff randomstuff Nov 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"inline" → "in line"?

Copy link
Collaborator

@randomstuff randomstuff Nov 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what to do about this part. I read it as "you'll have to care about it later" so I'm not sure it adds much information in its current form.

Copy link
Collaborator

@randomstuff randomstuff Nov 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe reword it as something like:

As there isn't any hardened code nor implementation reference available at the time of writing, this document currently does not recommend any Post-Quantum Cryptography (PQC) solution. An PQC implementation should be aligned with FIPS-203 and FIPS-204/205.

Loading