Comment 0 for bug 363092
Revision history for this message
| Björn Pettersson (bjorn-hygiena) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Using bzr release from yesterday.
Starting linuxdcpp I got a message saying the TLS port was busy and that I should change the TLS port in settings or close whatever application currently using that port.
I had set the TLS port to be the same as the regular TCP and UDP ports.This was what I did wrong.
It isn't obvious that it doesn't work with this setup, and even if it were obvious, I should not be allowed to set the TLS port tot be the same as any of the other two ports. (Or, if TLS only uses TCP, the TLS port should not be allowed to be the same as the regular TCP port.)