Posts

Showing posts from June, 2017

Security Updates: bind, httpd, libgcrypt

Patrick has issued several Slackware advisories today related to several packages:
bind: Upgraded to 9.9.10_P2, 9.10.5_P2, and 9.11.1_P2 (13.0 through - current)httpd: Upgraded to 2.2.32 and 2.4.26 (13.0 through - current)libgcrypt: Upgraded to 1.7.8 (14.2 and -current)kernel: Upgraded to 3.10.107 (only for 14.1) In -current, several packages gets bumped as well:
mkinitrd: Added support to include microcode and bumped to 1.4.10nano: Upgraded to 2.8.5screen: Upgraded to 4.6.0llvm: Upgraded to 4.0.1pcre: Upgraded to 8.40readline: Upgraded to 7.0.003xfdesktop: Upgraded to 4.12.4 It seems that several project are transititioning to Python 3 and some package in Slackware does require Python 3 in order to get bumped to new version. We will see if Python 3 finally gets approved to be included in the core packages and what other new package is included along with Python 3 inclusion.

Stack Clash Fixes

You may have heard about Stack Clash vulnerabilities that was published by Qualys last week. It was an old bug, but affected many systems running Linux both x86 and x86_64. As they coordinated the fixes with upstream vendors, the fixes has been released for public. Today's update is all about kernel update both in -stable (14.2 only) and -current. They are now upgraded to 4.4.74 and 4.9.34 which contains the fixes for Stack Clash. You are advised to upgrade your kernel as soon as possible. The other update that were both in -stable and -current are mozilla-thunderbird which is now updated to 52.2.1.

For those running -current, there are more updates in this batch:
lrzip: Upgraded to 0.631lvm2: Upgraded to 2.02.171time: Upgraded to 1.7.2mpg123: Upgraded to 1.25.0glib2: Upgraded to 2.52.3glibmm: Upgraded to 2.52.0gtkmm3: Upgraded to 3.22.1plus more in the past updates Users running Skylake/Kabylake processors should also read this thread on LQ about a bug in the Hyper-Threading featu…

Mid June Updates

More than 2 weeks since i gave an update to -current development and things are going more interesting in -current branch. It stays up-to-date with latest changes upstream while keeping the stability standards high. Here's some highlight in the last two weeks:
Kernel: Upgraded to 4.9.31Firefox: Upgraded to 52.2.0ESR releaseThunderbird: Upgraded to 52.2.0 release and switched to GTK+3NetworkManager: Upgraded to 1.8.0sqlite: Upgraded to 3.19.3bind: Upgraded to 9.11.1_P1gnupg2: Upgraded to 2.1.21gpgme: Upgraded to 1.9.0 (drop libgpgme-pthread support)pth -> npth replacementdirmngr removal (included in latest gnupg2)samba: Upgraded to 4.6.5glew: Upgraded to 2.0.0irssi: Upgraded to 1.0.3libdrm: Upgraded to 2.4.81mesa: Upgraded to 17.1.2gdb: Upgraded to 8.0sane: Upgraded to 1.0.27alsa-lib: Upgraded to 1.1.4.1cmake: Upgraded to 3.8.2mutt: Upgraded to 1.8.3 Due to the changes in the gnupg2 package, some startup scripts might need a little tweak. It dropped some options, so you might nee…

Migrating to x86_64

This evening, i decided to remove my Slackware-Current installation on my old Asus laptop which is still at 32 bit architecture and replace it with Slackware 14.2 64 bit architecture. The reason is simple: more and more upstream projects are supporting only for x86_64. Google, Facebook, Apple, and many big companies invest heavily on x86_64 architecture which has better future. It supports more memory without the use of PAE and better overall performance. Another reason is because i want to play more with Docker, which is (again) only available for x86_64 platform. Docker is now considered mature and ready to be deployed into production environments, so it's time to learn more about it.

I decided to stay with Slackware64 14.2 instead of going with -current for this laptop. I simply use the dual-side DVD of Slackware64-14.2 i got from Slackware Store and install it directly on the laptop. I formatted the old drive and in just under 15 minutes, the full installation is completed.

Ne…