This patch will report an error when it's the same and not set up the secure server... This is an untested patch, so I'd appreciate if someone could verify its functionality.
Note that I did not change the UI, so the user will only get an error when starting DC++ or setting the TCP/TLS ports. ** Patch added: "dcpp_tlsport.diff" https://bugs.launchpad.net/dcplusplus/+bug/363092/+attachment/3920444/+files/dcpp_tlsport.diff -- You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. https://bugs.launchpad.net/bugs/363092 Title: TLS port should not be allowed to be the same as regular ports Status in DC++: Confirmed Status in Linux DC++: Confirmed Bug description: 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 to 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.) To manage notifications about this bug go to: https://bugs.launchpad.net/dcplusplus/+bug/363092/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
