Security & certificates
Security certificates
The following are the paths of trusted certificate files. Default values are
empty which means the files will be created and loaded from a subfolder
named 'Certificates' located at the same folder as your DC++
settings files.
- Private key file
- This file is your personal and private certificate file. Do not share
this with other users or hubs. If you do, you risk allowing others to
use your certificate and in essence pose as you.
- Own certificate file
- This file is the certificate file you should give to other users and hubs
that you want to consider "trusted".
- Trusted certificates path
- Where trusted certificates from users or hubs will be stored. (default: the
"Certificates\" subdirectory of where you've installed the application.)
Secure connection settings
- Require TLS ADC client-client connections
- Enable this to force encrypted only transfers between clients in ADC
hubs. Note that this may result connection problems to clients that doesn't
properly support TLS versions and / or safe encryption methods that DC++
require.
- Allow TLS connections to hubs without trusted certificate
- With this option disabled, all hubs you connect to must have a certificate
in your Trusted certificate folder.
- Allow TLS connections to clients without trusted certificate
- With this option disabled, all client you connect to must have a certificate
in your Trusted certificate folder.
- Support direct encrypted private message channels
-
Enable support for peer-to-peer private messages that hubs can't spy upon.
Check the PM window help for more information.
- Always attempt to establish direct encrypted private message channels
-
Try to initiate a peer-to-peer connection whenever the user in private
message windows shows up. Check the PM window help for more
information.
To see effects, please restart DC++.
Note: TLS support is an experimental feature and doesn't imply that DC++ is
secure in any way.