> And, if I'm entirely honest, I think the server admins are worried that
> developers will unwittingly open up security holes, so instead of helping to
> educate the developers as to what is safe and not safe, prefer to take the
> "safest" route by just disallowing java all together.
<evil_rant>
Ok, that's just insane. I can see worrying about cold fusion security
risks based on the way the application is set up, or even using specific
apps, but the Java language as a whole?
That reeks of FUD. Not one line of IIS server code was written in java
and it is / has been full of holes, not to mention OSs in general. Java
removes a lot of buffer overflow, memory leak, and a slew of other
problems. I'd bet it would be be much harder to take a java based
program and exploit it enough to take control of a computer - which is
obviously done with other languages quite often. Leaving a variable open
for poison is not a Java problem btw.
I think your "server admins" don't understand it so they fear it, or
they are in the warm comfort zone of BB.
</evil_rant>
--
Vale,
Rob
Luxuria immodica insaniam creat.
Sanam formam viatae conservate!
http://www.rohanclan.com
http://treebeard.sourceforge.net
http://ashpool.sourceforge.net
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
