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 #?
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 #?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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
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.
ASKER