blog: AES-256-GCM Encryption — expand zero-dependency post for GSC striking-distance query - #210
Open
pstayets wants to merge 1 commit into
Open
Conversation
…riking-distance query Signed-off-by: pstayets <pstayets@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expands /blog/zero-dependency-encryption-x25519-aes-gcm for the GSC striking-distance query 'aes-256-gcm encryption' (pos 8.0, 0 clicks — a title/meta problem). Title and meta now lead with the target phrase, the first paragraph and one H2 carry it, the GCM section gains a CTR+GHASH deep-dive (how the mode authenticates, and the two invariants implementations must enforce), and two FAQs answer 'what is AES-256-GCM encryption?' and the AES-256-GCM vs ChaCha20-Poly1305 choice. Also syncs the matching blogPosts.json registry entry. Build + check:plain pass.