LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Tuesday, December 23rd, 2014
| Time |
Event |
| 2:26p |
NetworkManager 1.0.0 released Many of us have used NetworkManager for years, but the project only got around to putting out its 1.0.0
release now. " This release brings a more modern GObject-based
client library, many bug fixes and updated translations, more flexible
routing, hugely improved nmcli with password support, improved nmtui, a
light-weight internal DHCP client, 'configure and quit' mode, Bluetooth DUN
support with Bluez5, VPN connection persistence, improved cooperation with
external tools, expanded manpages and documentation, WWAN IPv6 support, and
much much more." | | 5:22p |
Tuesday's security updates Debian has updated cpio (denial of service).
Debian-LTS has updated eglibc (denial of service), firebird2.5 (denial of service), and jasper (two code execution vulnerabilities).
Gentoo has updated pdns-recursor
(multiple vulnerabilities, some from 2009).
Mageia has updated unrtf (code execution).
openSUSE has updated unbound
(13.2: denial of service).
Red Hat has updated kernel (RHEL6.4; RHEL6.2; RHEL5.9; RHEL5.6:
privilege escalation).
Slackware has updated ntp
(multiple code execution vulnerabilities), php (two vulnerabilities), and xorg (multiple vulnerabilities).
SUSE has updated ntp
(SLE11 SP3, SLES11 SP2: multiple code execution vulnerabilities). | | 6:50p |
Devuan progress report The people behind the Devuan project have released a progress
report. Devuan is a fork of Debian without systemd. A repository has been set up at GitLab. " This is the most recent achievement on infrastructure development: last night the first devuan-baseconf package was built correctly through our continuous integration infrastructure, pulling directly from our source repository." | | 10:17p |
[$] The "too small to fail" memory-allocation rule Kernel developers have long been told that, with few exceptions, attempts
to allocate memory can fail if the system does not have sufficient
resources. As a result, in well-written code, every call to a function
like kmalloc(), vmalloc(), or __get_free_pages()
is accompanied by carefully thought-out error-handling code. It turns out,
though, the behavior actually implemented in the memory-management
subsystem is a bit different from what is written in the brochure. That
difference can lead to unfortunate run-time behavior, but the fix might
just be worse.
Click below (subscribers only) for the full article from this week's Kernel
Page. |
|