It becomes readily apparent that Java may in fact be free from
program correctness flaws, but it isn't at all aparent that it is
free from other security flaws. The main problem I see, over and
over again, is that all the security is user configurable. This leaves
Java wide open to social engineering type attacks.. "Click here
for a really cool demo, and don't forget to disable network security!"
Not having to worry about the program accessing memory it shouldn't
and pointer abuses is good, but having file and network security
user configurable is scary. This is especially so when you've got 5000
undergraduates to worry about.
No amount of policy can prevent somebody from eventually doing something
wrong (or at least naive).
I'm still not reassured that I want to give this tool to everybody...
It still sounds easily subverted via social engineering. There are a lot
of things subject to this kind of attack, but something which sits out
on the web, looks "really cool", and might be fun, with explicit instructions
on how to get it to run by disabling something is just too easy. It could
even do something really cool, but be doing something not so cool behind
Doug Hughes Engineering Network Services
edu Auburn University