linuxdcpp-team team mailing list archive

Thread
Date

[Bug 363092] Re: TLS port should not be allowed to be the same as regular ports

To: linuxdcpp-team@xxxxxxxxxxxxxxxxxxx
From: eMTee <363092@xxxxxxxxxxxxxxxxxx>
Date: Tue, 12 Oct 2010 08:52:05 -0000
Reply-to: Bug 363092 <363092@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: dcplusplus
       Status: New => Confirmed

** Changed in: dcplusplus
   Importance: Undecided => Low

-- 
TLS port should not be allowed to be the same as regular ports
https://bugs.launchpad.net/bugs/363092
You received this bug notification because you are a member of LinuxDC++
Team, which is subscribed to LinuxDC++.

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.)