TLS port should not be allowed to be the same as regular ports
Bug #363092 reported by
Björn Pettersson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
AirDC++ |
Fix Released
|
Medium
|
Unassigned | ||
DC++ |
Fix Released
|
Low
|
Unassigned | ||
LinuxDC++ |
Confirmed
|
Low
|
Unassigned |
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.)
description: | updated |
Changed in dcplusplus: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: core |
tags: | added: win32-ui |
Changed in airdcpp: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in dcplusplus: | |
status: | In Progress → Fix Committed |
Changed in airdcpp: | |
status: | Confirmed → Fix Committed |
Changed in airdcpp: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
For your info, It's just TCP. :)