Skip to main content

Important Java Update

As you probably know, Oracle has released an update for Java 6 SE (JDK/JRE) Update 26 which contains a security fixes according to the release notes and more detail information can be seen on Oracle's website here and here. You might ask, why Slackware hasn't release any update for this packages on -Stable and also on -Current?

Actually there's someone who asked me this question few days ago via email. At first, i didn't see the security fixes mentioned at the release note, so i said to him that Slackware's policy is not to update any packages in -Stable unless there's a security vulnerabilities (moreover when they have CVE entries). He sent me another page (which was those two URL in Oracle's website above) that described the cumulative update for for JDK/JRE package and it affects previous Java 6 Update 25 and it has 17 CVEs Big Eyes. Yes, 17 CVEs, but some (or most) of it only exists on Windows platform, so i don't mind about it too much.

Later on, i found out that Slackware's policy is not to update blob packages (like those JDK/JRE) in -Stable releases (Thanks to Pat for the info). It will be updated on -Current only. Users of -Stable releases will have to work on their own to fix this problem. Actually, it's super duper easy to do that. As you know, users can always get the SlackBuild script on the source/ directory and get the source for the new JDK/JRE package and edit the VERSION line to build the new package for their own need. It's that simple Rolling

Since it contains quite a lot of security fixes, it's recommended to upgrade to the latest version if you happened to use Java applications or often browsing to websites which uses Java applet frequently.

Popular posts from this blog

Running Rsync Via Proxy

One way to get the latest Slackware updates is by running rsync to syncronize your local repository and the main repository that hold the Slackware packages. Eric Hameleers has provided a great script called rsync_current.sh and how i modified this tool has been discussed on my previous post. In general, it works, except for one problem, when your computer is connecting to the Internet through a proxy.

My workstation at my office is connected to the Internet through a proxy, so i can't use normal rsync to work normally. I browsed the web and i found this site which tells us about how we should modify our squid configuration to allow rsync connection from any computer from our local networks. I asked my sysadmin to try this script. He agreed and he updated the squid configuration on the proxy.

Next, i need to update my environment variable RSYNC_PROXY to the host of the proxy and also the port. Let's say you are running a proxy on 192.168.1.1 and port 8080, then you need to run …

NVidia Legacy Unix Driver Update

NVidia has released an updated legacy drivers to support X.Org 1.19 with ABI 23. It has been mentioned in the UNIX drivers, but you can directly find the drivers from the links below:
NVidia 304.134 (x86x86_64)NVidia 340.101 (x86, x86_64) I have tested the 304.134 driver and it's working great here. I can finally remove x from my /etc/slackpkg/blacklist file since it's a showstopper for me.
Aside from legacy driver, NVidia has also released their latest driver 375.26 (x86, x86_64), which brings support for newer cards and also many new features (including X.Org 1.19 with ABI 23 support). 

Security Update: firefox, irssi, pidgin

Three security updates were released for today:
firefox: Upgraded to 45.4.0esr for 14.1 and 14.2 and 49.0 for currentirssi: Upgraded to 0.8.20pidgin: Upgraded to 2.10.11, 2.10.12, and 2.11.0 for all stable Slackware releases depending on their support Some minor update in current:
mkinitrd: Add dmsetup supportemacs: Upgraded to 25.1qt: Fix multilib issue network-scripts: Fix minor issue