Re:JDK 7u11 Release Notes
by drivebyacct2 on Sunday January 13, 2013 @10:43PM
(#5053181)
I am willing to take my chances with the security record and response of the Chrome team over Adobe or Oracle's.
People used to say the same thing about Java. When you can write a web app for Chrome that can do the same sorts of things applets can do, you're going to see the same sorts of exploits. The problem isn't that the Sun and Oracle people didn't know what they were doing. The problem is your opportunities for security problems scale with the amount of functionality you're delivering.
Re:JDK 7u11 Release Notes
by drivebyacct2 on Monday January 14, 2013 @12:26AM
(#5053403)
You can do almost anything you can do in an applet, now from NaCl/PNaCl or from Javascript (including TCP/UDP sockets, etc) when writing a Chrome CRX or CRX-less webapp that the user opts to install.
Maybe you're right, we'll see. That having been said, again, with Chrome's track record, update schedule, update mechanics and more, I'm trusting them a huge factor more than Oracle. Also, keeping in mind that having different implementations across 2-3 major web browsers dampens the effect of having an exploit in one.
I don't know why you would think browser native technology will be any more secure. Java and Flash aren't heavily exploited because they're worse than other products - they're exploited because they're ubiquitous. And it's not like we don't have manufacturers to hold accountable here, whatever that means.
Security is hard. It's really, really, really hard to add new functionality without leaving a chink in your security armor. This cycle of 0-day exploits is not going away even when Flash and Java are only discussed in nursing homes.