LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Tuesday, June 14th, 2016
| Time |
Event |
| 1:03p |
Git v2.9.0 released
Version 2.9.0 of the Git source-code management system is out. There are
various improvements and small changes that maintainers of scripts using
Git will want to look at, but no major changes. | | 3:48p |
Security updates for Tuesday Debian has updated icedove (code execution).
Debian-LTS has updated libav (code execution).
openSUSE has updated libtasn1
(13.2: two denial of service vulnerabilities) and nodejs (Leap42.1, 13.2: multiple vulnerabilities).
Oracle has updated kernel 4.1.12 (OL7; OL6:
privilege escalation), kernel 3.8.13 (OL7; OL6:
privilege escalation), kernel 2.6.39 (OL6; OL5:
privilege escalation).
Red Hat has updated kernel
(RHEL6.5: two remote denial of service vulnerabilities).
SUSE has updated ImageMagick
(SLE12-SP1: command execution) and ntp (SLE12-SP1; SLE12: multiple vulnerabilities). | | 6:56p |
Ubuntu’s snap apps are coming to distros everywhere (Ars Technica) Ars Technica reportsthat Ubuntu's snapd tool has been ported to other Linux distributions. " To install snap packages on non-Ubuntu distributions, Linux desktop
and server users will have to first install the newly cross-platform
snapd. This daemon verifies the integrity of snap packages, confines them
into their own restricted space, and acts as a launcher. Instructions for
creating snaps and installing snapd on a variety of distributions are
available at this website.
Snapd itself is installed as traditional packages on these other operating
systems. That means there's a snapd RPM package for Fedora, for
example. It's the same snapd code for every Linux distribution, just
packaged differently, and applications packaged as snaps should work on any
Linux distro running snapd without needing to be re-packaged." Snapd is available for Arch, Debian, and Fedora. It's also being tested by CentOS, Elementary, Gentoo, Mint, openSUSE, OpenWrt and RHEL. | | 9:44p |
[$] Kernel building with GCC plugins
It has long been understood that static-analysis tools can be useful in
finding (and defending against) bugs and security problems in code. One of
the best places to implement
such tools is in the compiler itself, since much of the work required to
analyze a program is already done in the compilation process. Despite the
fact that GCC has had the ability to support security-oriented plugins for
some years, the mainline kernel has never adopted any such plugins. That
situation looks likely to change with the 4.8 kernel release, though. |
|