[tor-commits] [pluggable-transports/obfs4] 01/08: doc: Correct why the obfs4 change is backward compatible (NFC)

[gitolite role <git@xxxxxxxxxxxxxxxxxxxxx>]

This is an automated email from the git hooks/post-receive script.

meskio pushed a commit to branch master
in repository pluggable-transports/obfs4.

commit d5a51619ebe50fb5cd5b5060c2e57c99826543a8
Author: Yawning Angel <yawning@xxxxxxxxxxxxxxx>
AuthorDate: Thu Jan 27 07:55:29 2022 +0000

    doc: Correct why the obfs4 change is backward compatible (NFC)
---
 internal/README.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/internal/README.md b/internal/README.md
index 05aa472..a2a6e2b 100644
--- a/internal/README.md
+++ b/internal/README.md
@@ -13,10 +13,9 @@ be it via the modified scalar basepoint multiply or via decoding a
 representative will be somewhat non-standard, but will interoperate with
 a standard X25519 scalar-multiply.
 
-As the obfs4 handshake does not include the decoded representative in
-any of it's authenticated handshake digest calculations, this change is
-fully-backward compatible (though the non-upgraded side of the connection
-will still be trivially distinguishable from random).
+As the representative to public key transform should be identical,
+this change is fully-backward compatible (though the non-upgraded side
+of the connection will still be trivially distinguishable from random).
 
 ##### Maintainer's rant
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits