linuxdcpp-team team mailing list archive

[Sopor <363092@xxxxxxxxxxxxxxxxxx>]

This would be nice if this could be fixed in AirDC++ too. Too many users
are mixing this up and write the same port number in TLS as they use in
TCP...

-- 
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++:
  Confirmed
Status in DC++:
  Fix Released
Status in LinuxDC++:
  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