linuxdcpp-team team mailing list archive
-
linuxdcpp-team team
-
Mailing list archive
-
Message #07778
[Bug 363092] Re: TLS port should not be allowed to be the same as regular ports
This patch will add popups when the user tries to set invalid values.
Also, it will write an empty string if the value is the same as as
another port.
** Patch added: "dcpp_tlsport.diff"
https://bugs.launchpad.net/dcplusplus/+bug/363092/+attachment/3920791/+files/dcpp_tlsport.diff
** Changed in: dcplusplus
Status: Confirmed => In Progress
--
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 AirDC++:
New
Status in DC++:
In Progress
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/airdcpp/+bug/363092/+subscriptions