Link to home
Start Free TrialLog in
Avatar of trojan81
trojan81

asked on

TCP ports - changing

Hello TCP experts,

This may be a dumb question. Suppose I have an application that listens on TCP 3012. Suppose I want to secure it with SSL. I know of a handful of TCP ports with SSL "flavors" (ldaps, imaps, pop3s, etc).
I was thinking if I change the app to listen on, let's say, tcp 636, would I then be able to secure it with an SSL Cert? I guess what I'm missing is, are port #s, just numbers or is it the behavior of the traffic that defines the port #?
Avatar of trojan81
trojan81

ASKER

Giving it a second thought and I think simply configuring your application to listen on a known secure port over SSL doesnt do any good if the application is not configured to negotiate encryption with the client. Is that a correct assumption?
ASKER CERTIFIED SOLUTION
Avatar of theras2000
theras2000
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thereas2000

Your comment "Yes that's correct.  You can just change your port and expect your application to automatically encrypt traffic."

Did you mean to say You CAN'T or you CAN
Do'h!  You CAN'T.  Sorry about the typo.