I'm using Firefox in Ubuntu with Java to connect to a Juniper Networks VPN. When I upgraded to Ubuntu 13.10 a couple of days ago, the VPN launcher stopped working. I think Firefox 24 came along with the upgrade (that's the version running now). I upgraded to the latest Java r45 and it still didn't work. Then I noticed a blinking red thing in the address bar where the security lock icon goes. I clicked that and it gav…
In Firefox 24 and following, mark all versions of Java as unsafe
61–70 of 184 posts
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#62I'm using Firefox in Ubuntu with Java to connect to a Juniper Networks VPN. When I upgraded to Ubuntu 13.10 a couple of days ago, the VPN launcher stopped working. I think Firefox 24 came along with the upgrade (that's the version running now). I upgraded to the latest Java r45 and it still didn't work. Then I noticed a blinking red thing in the address bar where the security lock icon goes. I clicked that and it gav…
https://support.mozilla.org/en-US/kb/how-to-enable-java-if-i...
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#63I'm all for this being blocked by default, and the same goes for all plugins. But it certainly bothers me when they make it impossible to override their security constraints. Put in an about:config setting to allow Java, and it's fine. All the heavy-handedness is going to do is force Firefox out of corporate IT environments where many internal websites rely on Java.
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#64Earlier quoted context omitted.
Except it's not getting replaced, it's getting blocked and disabled. While lots of code deployed still depends on it. I hate Java applets as much as the next guy, but lets not ignore that there's a real world out there.
The real world would be nicer if Oracle actually worked on fixing Java security issues. They have a bad history of pretending that security holes have been fixed and/or pretending that they do not exist, while exploits run rampant.
+ Fork if legally required.
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#65A lot of the commenters here seem to misunderstand this change. You can still easily run Java applets in Firefox 24 and beyond, you just need to click the red lego block in the upper left corner and allow it. [1] It's much less strict than in Chrome (on OS X), where Java doesn't run at all anymore. [1] https://support.mozilla.org/en-US/kb/how-to-enable-java-if-i...
I've had multiple calls in the past week from Java users who didn't know that and just thought the page in question had stopped working. Your idea of "easily" and theirs are very different.
It's much less strict than in Chrome, where Java doesn't run at all anymore.
I've spent much of this morning testing applets in Chrome. In fact, I've got one running right now, and I just confirmed that Chrome is up-to-date. Perhaps you've misunderstood something?
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#66Re: In Firefox 24 and following, mark all versions of Java as unsafe
#67Earlier quoted context omitted.
Will it? I've been browsing without Java for years, and I can only remember problems with one site (some hilarious throwback from the late 90s). For general browsing, I doubt anyone will notice a difference. Maybe for corporate use, but isn't that mostly IE anyway?
Depends on where you are in the world. Java is required for online banking in Norway, while it's mostly unused in Sweden, the neighbouring country. Both use Java for online verification to government sites.
Do they? I thought Sweden used the online bank identity system for verification (bankid), which is either a standalone downloadable application, a smartcard image, or an mobile app. Not sure how an Firefox policy would effect this even if some parts of the bankid uses Java.
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#68Earlier quoted context omitted.
Sure, and I haven't used Internet Explorer in years. That doesn't mean that suddenly disabling Internet Explorer is going to have no effect even if I (and probably most of us here on HN) would not even notice. A lot of corporates and financial applications require Java.
So you think perpetuating the use of Java in the browser is a reasonable response to the security risks it presents to those corporates? This action by Mozilla raises awareness of the fact that Java security updates are too slow and too opaque and it's time to change to something else.
It also raises awareness of the fact that you can't trust some of the big names in the browser industry not to break stuff every few weeks just because they don't like it and then push the changes on you whether you want them or not.
Introducing restrictions so tight that you can't actually do your useful work any more isn't security, it's just broken.
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#69A lot of the commenters here seem to misunderstand this change. You can still easily run Java applets in Firefox 24 and beyond, you just need to click the red lego block in the upper left corner and allow it. [1] It's much less strict than in Chrome (on OS X), where Java doesn't run at all anymore. [1] https://support.mozilla.org/en-US/kb/how-to-enable-java-if-i...
You can still easily run Java applets in Firefox 24 and beyond, you just need to click the red lego block in the upper left corner and allow it. I've had multiple calls in the past week from Java users who didn't know that and just thought the page in question had stopped working. Your idea of "easily" and theirs are very different. It's much less strict than in Chrome, where Java doesn't run at all anymore. I've spe…
Still, it's a much easier thing for normal users to figure out than how to update Java (which they must do quite regularly to get Java to run at all).
I did a little Googling and it turns out that Java still runs in Chrome on Windows, it's just banned on OS X.
Re: In Firefox 24 and following, mark all versions of Java as unsafe
#70A lot of the commenters here seem to misunderstand this change. You can still easily run Java applets in Firefox 24 and beyond, you just need to click the red lego block in the upper left corner and allow it. [1] It's much less strict than in Chrome (on OS X), where Java doesn't run at all anymore. [1] https://support.mozilla.org/en-US/kb/how-to-enable-java-if-i...
You can still easily run Java applets in Firefox 24 and beyond, you just need to click the red lego block in the upper left corner and allow it. I've had multiple calls in the past week from Java users who didn't know that and just thought the page in question had stopped working. Your idea of "easily" and theirs are very different. It's much less strict than in Chrome, where Java doesn't run at all anymore. I've spe…