docs: update PQC guide to follow standard template format - #14333
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request simplifies the Post-Quantum Cryptography (PQC) documentation by streamlining the overview, updating section headers, and reducing external links to a single resource. The review feedback suggests improving consistency by capitalizing "Post-Quantum" in the headers and formatting the technical identifier X25519MLKEM768 as inline code for better readability.
| @@ -1,16 +1,12 @@ | |||
| # Post-Quantum Cryptography (PQC) User Guide for Google Cloud Java Client Libraries | |||
| # Post-quantum Cryptography (PQC) Support | |||
There was a problem hiding this comment.
For consistency with the rest of the document (such as line 3), "Post-Quantum" should be capitalized with a capital "Q".
| # Post-quantum Cryptography (PQC) Support | |
| # Post-Quantum Cryptography (PQC) Support |
| For more information on Google Cloud's approach, see [Post-Quantum Cryptography on Google Cloud](https://cloud.google.com/security/resources/post-quantum-cryptography?hl=en). | ||
|
|
||
| To defend against this without sacrificing stability, Google Cloud Java client libraries adopt **Hybrid Key Exchange** (combining classical algorithms like `X25519` with standardized post-quantum algorithms like `ML-KEM-768`). This ensures connections remain secure even if an unforeseen mathematical weakness is discovered in either algorithm. | ||
| ## Post-quantum key exchange |
There was a problem hiding this comment.
For consistency with the rest of the document, "Post-Quantum" should be capitalized with a capital "Q".
| ## Post-quantum key exchange | |
| ## Post-Quantum key exchange |
| - [How Google is preparing for a post-quantum world](https://cloud.google.com/blog/products/identity-security/how-google-is-preparing-for-a-post-quantum-world/?e=48754805) | ||
| - [PQC in Plaintext: Google Cloud's Post-Quantum Cryptography Roadmap](https://cloud.google.com/blog/products/identity-security/pqc-in-plaintext-google-clouds-post-quantum-cryptography-roadmap) | ||
| - [Post-Quantum Cryptography Standards: What you need to know](https://security.googleblog.com/2024/08/post-quantum-cryptography-standards.html) | ||
| Google Cloud client libraries support post-quantum key exchange using the X25519MLKEM768 hybrid mechanism for TLS 1.3 connections. |
There was a problem hiding this comment.
The hybrid mechanism identifier X25519MLKEM768 should be formatted as inline code (using backticks) to improve readability and distinguish it as a technical identifier.
bc13607 to
87d5913
Compare
87d5913 to
dd6b2da
Compare
1 participant
This PR updates
docs/post_quantum_cryptography_guide.mdto follow the official Google Cloud Post-Quantum Cryptography documentation template format and moves external reading links to an Additional Resources section at the bottom.Stacked on top of #14245.