gui, man, authors: Update docs, translations, and contributors

man/syncthing-security.7

@@ -1,6 +1,6 @@
 .\" Man page generated from reStructuredText.
 .
-.TH "SYNCTHING-SECURITY" "7" "Jan 24, 2020" "v1" "Syncthing"
+.TH "SYNCTHING-SECURITY" "7" "Feb 02, 2020" "v1" "Syncthing"
 .SH NAME
 syncthing-security \- Security Principles
 .
@@ -40,7 +40,7 @@ All device to device traffic is protected by TLS. To prevent uninvited devices
 from joining a cluster, the certificate fingerprint of each device is compared
 to a preset list of acceptable devices at connection establishment. The
 fingerprint is computed as the SHA\-256 hash of the certificate and displayed
-in BASE32 encoding to form a reasonably compact and convenient string.
+in a human\-friendly encoding, called Device ID.
 .sp
 Incoming requests for file data are verified to the extent that the requested
 file name must exist in the local index and the global model.
@@ -115,11 +115,10 @@ usage reporting server itself may expose the client as running Syncthing.
 .SS Sync Connections (BEP)
 .sp
 Sync connections are attempted to all configured devices, when the address is
-possible to resolve. The sync connection is based on TLS 1.2. The TLS
-certificates are sent in clear text (as in HTTPS etc), meaning that the
-certificate Common Name (by default \fBsyncthing\fP) is visible.
+possible to resolve. The sync connection is based on TLS 1.2 or TLS 1.3. The TLS
+certificates can be obtained by an eavesdropper, altough it is more difficult to do so in TLS 1.3. This means that the contents of the certificate are visible, which includes certificate Common Name (by default \fBsyncthing\fP).
 .sp
-An eavesdropper can deduce that this is a Syncthing connection and calculate the
+An eavesdropper can deduce that this is a Syncthing connection and under certain circumstances calculate the
 device IDs involved based on the hashes of the sent certificates.
 .sp
 Likewise, if the sync port (default 22000) is accessible from the internet, a