TCP ports - changing
Posted on 2013-01-17
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 #?