Why are developers choosing to...

["Behm, Jeffrey L." <BehmJL () bvsg com>]

Why are developers choosing to write "web-based" code that runs some
sort of encryption, typically SSL, across a non-standard port (say
10443) and then having those URLs blow up when they try to traverse the
prudent company's perimeter security...You know..."deny all that is not
explicitly allowed."

I am seeing more and more "websites" that use a URL such as
http://register.at.my.site:10443. Why not just use the standard secure
port 443 from the get go?  Is there something that makes SSL across
10443 innately more secure, or is this just the "security by obscurity"
smoke-and-mirrors trick?

Opinions?

Jeff
_______________________________________________
firewall-wizards mailing list
firewall-wizards () honor icsalabs com
http://honor.icsalabs.com/mailman/listinfo/firewall-wizards