This is a discussion on Re: [fw-wiz] Why are developers choosing to... - Firewalls ; Here is my admittedly jaundiced opinion. In the last few years I see more and more developers who work in a GUI IDE, and don't understand basic concepts. For example, the concept of a network port. I had one developer ...
Here is my admittedly jaundiced opinion. In the last few years I see more
and more developers who work in a GUI IDE, and don't understand basic
concepts. For example, the concept of a network port. I had one developer
that insisted his application didn't listen on a port, it used the
subnet. Some of them don't understand the concept of a directory
I am starting to blame a lot of this on GUI development products. I am
trying to be nice and not completely blame the developers and the bozo
managers who hire them. The IDE takes care of everything other than the
actual code by using various default settings. This leaves the developers
without any reason to learn what environment the application has to work
in. It works in their GUI, doesn't it?
At 09:34 AM 1/20/2006, Behm, Jeffrey L. wrote:
>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
>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"
firewall-wizards mailing list