There is an update to Chrome/Chromium which arrives in very close succession to the previous update less than two weeks ago. The version number change is minimal, 32.0.1700.77 to 32.0.1700.102, but it addresses several vulnerabilities, so it is advised to update your Chrome and/or chromium packages.
The most important fixes are:
[$1000] High CVE-2013-6649: Use-after-free in SVG images. Credit to Atte Kettunen of OUSPG.
[$3000] High CVE-2013-6650: Memory corruption in V8. This issue was fixed in v8 version 220.127.116.11. Credit to Christian Holler.
I have packages ready for the new chromium:
- http://slackware.com/~alien/slackbuilds/chromium/ (primary server)
- http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/chromium/ (my own US mirror)
- http://alien.slackbook.org/slackbuilds/chromium/ (US)
- http://slackware.org.uk/people/alien/slackbuilds/chromium/ (UK)
You can subscribe to the repository’s RSS feed if you want to be the first to know when new packages are uploaded.
Pretty quickly after IcedTea 2.4.4, we can now download 2.4.5 from the web site. This is purely a bugfix release (no security issues are addressed) and the new build brings OpenJDK to version “Update 51 Build 31“, thus synchronizing with the upstream’s source tag “u51 b31”. Read GNU/Andrew’s release notes if you want to know what has been fixed.
My functionality tests (jMol and Minecraft) were satisfactory 🙂 Please note that Firefox and Chrome/Chromium browsers no longer load Java applets (or other plugins) by default and ask you for explicit approval to load and run them.
My new packages have again been compiled on Slackware 13.37. They are usable on 13.37 as well as 14.0, 14.1 and -current! Get them preferably from a mirror site (faster downloads):
- http://slackware.com/~alien/slackbuilds/openjdk/ , the primary location
- http://alien.slackbook.org/slackbuilds/openjdk/ , the community mirror (bandwidth-capped)
- http://taper.alienbase.nl/mirrors/people/alien/slackbuilds/openjdk/ , my own fast US mirror
- http://slackware.org.uk/people/alien/slackbuilds/openjdk/ , fast UK mirror, needs a day to get in sync
Further packages that are recommended/required:
- Optional: If you want a Java browser-plugin you must install icedtea-web (OpenJDK itself does not contain such a plugin).
Note that you should only install one of the two packages, either openjdk or openjre, do not install both at the same time or things will break! The openjdk package contains the jre (java runtime) as well as the java development kit.
Hi Eric, there is any update for Slackware 14.0 on Chromiun?
I had found nothing since the 24th version of it.
Hi p431i7o –
I never created chromium packages for Slackware 14.0 and they are not going to arrive either. You’ll have to be using Slackware 14.1 or -current.
That does not mean it won’t compile… I just did not bother because it is a large project and would take too much of my time. You can try compiling it yourself.
Thanks again Eric!
The chromium package updated yesterday through Slackpkg+ It also grabbed a new pipelight and related stuff.
Please note that Firefox and Chrome/Chromium browsers no longer load
I think part of this missing?
It was a text formatting issue… I removed a couple of ‘span’ html elements that WordPress had added by itself, and it looks OK again.
You need add a link in /usr/lib/java/jre/bin/java to /usr/bin/java.
Always I install a new system, the java command is not found. Put a ln comand in the package.
Thank you for the excellent work.
No, a symlink is not needed. You need to logoff and login again to update your environment. The java packages (my own openjdk and openjre, and SLackware’s jdk in the /extra section) add profile scripts to directory ” /etc/profile.d/ ” which need to be executed – for instance, that will happen everytime you login. The scripts expand the $PATH and $MANPATH variables and set a new variable $JAVA_HOME .
Else if you do not want to re-login straight away, you can run the command ” . /etc/profile ” in the terminal where you need java.
Minor typo – the Chromium version is 32.x, not 30.x as stated in your post
Well noted! I have updated the main article, thanks.