From 8a4cb7650850a5b74882be714353362e86f74789 Mon Sep 17 00:00:00 2001 From: Hollow Man Date: Sat, 6 Feb 2021 02:29:43 +0800 Subject: [PATCH] Fix typos (#969) accidentially -> accidentally neglible -> negligible --- docs/adrs/0297-base64-masking-trailing-characters.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/adrs/0297-base64-masking-trailing-characters.md b/docs/adrs/0297-base64-masking-trailing-characters.md index 24cbfd9a6..4bd072311 100644 --- a/docs/adrs/0297-base64-masking-trailing-characters.md +++ b/docs/adrs/0297-base64-masking-trailing-characters.md @@ -15,7 +15,7 @@ This gives us good coverage across the board for secrets and secrets with a pref However, we don't have great coverage for cases where the secret has a string appended to it before it is base64 encoded (i.e.: `base64($pass\n))`). -Most notably we've seen this as a result of user error where a user accidentially appends a newline or space character before encoding their secret in base64. +Most notably we've seen this as a result of user error where a user accidentally appends a newline or space character before encoding their secret in base64. ## Decision @@ -45,4 +45,4 @@ This will result in us only revealing length or bit information when a prefix or - In the case where a secret has a prefix or suffix added before base64 encoding, we may now reveal up to 20 bits of information and the length of the original string modulo 3, rather then the original 16 bits and no length information - Secrets with a suffix appended before encoding will now be masked across the board. Previously it was only masked if it was a multiple of 3 characters -- Performance will suffer in a neglible way +- Performance will suffer in a negligible way