Secure unsigned Java Web Start applications
Secure unsigned Java Web Start applications
Posted Sep 12, 2003 4:26 UTC (Fri) by MarkSwanson (guest, #9328)Parent article: Software Customer Bill of Rights
>They don't need to reverse engineer the software to check for security holes or to fix
>bugs and security glitches -- they already have the source code. (Nothing in any
This idea is a failure because only a handful of people will have the skill, inclination or
time to find and fix bugs and security glitches.
The closest to perfect solution is to run your application inside of
a Java Web Start (JWS) secure sandbox.
>While "spyware" is a constant danger >posed by proprietary software, with access
>to source code, users can make sure that >a program isn't secretly sending data off
>of their computer to another machine.
Again, this idea is a failure for the same reason stated above.
Remember that unsigned JWS applications prevent "spyware" from working at all.
In fact, here's a great concept that doesn't get enough attention: you do not have to
trust the software vendor when you are running unsigned JWS code. That's the kind of
world I'd like to live in. Yes, If I give the vendor my email address I may have to trust
them not to sell it to a spammer - you know that's not what I'm talking about. I'm
merely mentioning what most of you already know - secure access to the hard drive,
network, keyboard, clipboard, video, etc.
Cheers.
