modified: en/Archive/Development/GPGAuthentication

User Summary: removing gendered language

Author: BasicBeluga

Page/en/Archive/Development/GPGAuthentication.mediawiki

@@ -39,7 +39,7 @@ At this point, both server and client have each other's public keys, and authent
 
 == NOTES ==
 
-# Username / password is not needed. The GPG key acts as the username, and the password authentication is done locally on a user's computer through the GPG program. GPG encryption is considered extremely secure, and the only way to pass off as another user would be to get a hold of both his private key and his password.
+# Username / password is not needed. The GPG key acts as the username, and the password authentication is done locally on a user's computer through the GPG program. GPG encryption is considered extremely secure, and the only way to pass off as another user would be to get a hold of both their private key and their password.
 # Because all communication both ways are encrypted and signed, putting up a man-in-the-middle attack is extremely cumbersome. Because the server owner is given the client's key on beforehand, the person attempting man-in-the-middle attack would actually have to disrupt this process first, which can be near-impossible, before even having a chance at the man-in-the-middle-attack in the first place.
 
 == [[en/Archive/Development/Miscellaneous suggestions/Centralised authentication]] ==