gui, man, authors: Update docs, translations, and contributors
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
.\" Man page generated from reStructuredText.
|
||||
.
|
||||
.TH "SYNCTHING-SECURITY" "7" "Jul 28, 2020" "v1" "Syncthing"
|
||||
.TH "SYNCTHING-SECURITY" "7" "Aug 04, 2020" "v1" "Syncthing"
|
||||
.SH NAME
|
||||
syncthing-security \- Security Principles
|
||||
.
|
||||
@@ -116,7 +116,7 @@ usage reporting server itself may expose the client as running Syncthing.
|
||||
.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 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).
|
||||
certificates can be obtained by an eavesdropper, although 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 under certain circumstances calculate the
|
||||
device IDs involved based on the hashes of the sent certificates.
|
||||
|
||||
Reference in New Issue
Block a user