ncdc 1.23.1 + checksums + updates
This commit is contained in:
parent
db0e63dbf3
commit
aad45f7196
71 changed files with 359 additions and 27 deletions
|
|
@ -609,11 +609,11 @@ Set the policy for sending or receiving encrypted UDP search results. When set t
|
|||
|
||||
Note that, regardless of this setting, encrypted UDP search results are only used on ADCS hubs. They will never be sent on NMDC or non-TLS ADC hubs. Also note that, even if you set this to `prefer', encryption is still only used when the client on the other side of the connection also supports it.
|
||||
|
||||
=item B<tls_policy> <disabled|allow|prefer>
|
||||
=item B<tls_policy> <disabled|allow|prefer|force>
|
||||
|
||||
Set the policy for secure client-to-client connections. Setting this to `disabled' disables TLS support for client connections, but still allows you to connect to TLS-enabled hubs. `allow' will allow the use of TLS if the other client requests this, but ncdc itself will not request TLS when connecting to others. Setting this to `prefer' tells ncdc to also request TLS when connecting to others.
|
||||
Set the policy for secure client-to-client connections. Setting this to `disabled' disables TLS support for client connections, but still allows you to connect to TLS-enabled hubs. `allow' will allow the use of TLS if the other client requests this, but ncdc itself will not request TLS when connecting to others, `prefer' tells ncdc to request TLS when connecting to others. Setting this to 'force' will disallow non-TLS connections and also requires that the hub connection itself is TLS.
|
||||
|
||||
The use of TLS for client connections usually results in less optimal performance when uploading and downloading, but is quite effective at avoiding protocol-specific traffic shaping that some ISPs may do. Also note that, even if you set this to `prefer', TLS will only be used if the connecting party also supports it.
|
||||
The use of TLS for client connections usually results in less optimal performance when uploading and downloading, but is quite effective at avoiding protocol-specific traffic shaping that some ISPs may do.
|
||||
|
||||
=item B<tls_priority> <string>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue