3 ms·
For the devs on Linux who actually need Java (e.g. Java or Clojure or Scala devs etc.), then there's an easy way out. Do NOT install Java from your distro. Do
by martinced 14y ago
For the devs on Linux who actually need Java (e.g. Java or Clojure or Scala devs etc.), then there's an easy way out.
Do NOT install Java from your distro. Do NOT install Java by giving the root password (or by directly using the root account): no rpm, no deb.
Fetch, from a regular user account, the Java .tar.gz and install Java in your dev user account.
And then install your browser in another user account.
This is what I do.
This way you can be sure and certain that no amount of Sun / Oracle uber retardedness Java applets can ruin your day....
- yuhong 14y agoI wonder if IcedTea could lead by provinding a faster patch cycle.
- stusmall 14y agoOr you can just disable the java plugins in your browsers. I think that might be slight overkill
- acdha 14y ago> Do NOT install Java from your distro. Do NOT install Java by giving the root password (or by directly using the root account): no rpm, no deb. This advice is fundamentally confused about how computer security works: the issue is not how the code is installed, it's whether an attacker can get your browser / email client to execute it. If the code runs as you, it has all the access it needs even if the files are owned by root. > Fetch, from a regular user account, the Java .tar.gz and install Java in your dev user account. So I don't get updates from the very responsive Ubuntu / Debian groups and instead rely on obsessively checking the news? That seems a LOT worse than simply disabling the Java browser plugin.