Tuesday, June 28th, 2016

Time	Event
4:09p	Tuesday's security advisories Debian has updated kernel (multiple vulnerabilities). Debian-LTS has updated movabletype-opensource (SQL injection) and spice (information disclosure). Fedora has updated drupal7 (F23; F22: privilege escalation), gd (F24: three vulnerabilities), krb5 (F24: buffer overflow), nodejs (F24: unspecified), and phpMyAdmin (F24: multiple vulnerabilities). Gentoo has updated icedtea-bin (multiple vulnerabilities) and kwalletd (misuse of crypto). openSUSE has updated rsync (13.2: unsafe destination path). SUSE has updated firefox, nss, nspr (SLE12-SP1: multiple vulnerabilities) and kernel (SLE12-SP1; SLE12: multiple vulnerabilities). Ubuntu has updated kernel (16.04; 15.10; 14.04; 12.04: multiple vulnerabilities), linux-lts-trusty (12.04: multiple vulnerabilities), linux-lts-utopic (14.04: multiple vulnerabilities), linux-lts-vivid (14.04: multiple vulnerabilities), linux-lts-wily (14.04: multiple vulnerabilities), linux-lts-xenial (14.04: multiple vulnerabilities), linux-raspi2 (16.04; 15.10: multiple vulnerabilities), linux-snapdragon (16.04: multiple vulnerabilities), and linux-ti-omap4 (12.04: multiple vulnerabilities). (Comment on this)
8:29p	GitHub's 2015 Transparency Report GitHub has published its 2015 transparency report. "This 2015 report details the types of requests we receive for user accounts, user content, information about our users, and other such information, and how we process those requests. Transparency and trust are essential to GitHub and to the open source community, and giving you access to information about these requests can protect you, protect us, and help you feel safe as you work on GitHub." The report notes that a significant number of requests for removal of content are notices submitted under the Digital Millennium Copyright Act, or the DMCA. (Comment on this)
10:37p	[$] How many -stable patches introduce new bugs? The -stable kernel release process faces a contradictory set of constraints. Developers naturally want to get as many fixes into -stable as possible but, at the same time, there is a strong desire to avoid introducing new regressions there. Each -stable release is, after all, intended to be more stable than its predecessor. At times there have been complaints that -stable is too accepting and too prone to regressions, but not many specifics. But, it turns out, this is an area where at least a little bit of objective research can be done. (Comment on this)

<< Previous Day

2016/06/28 [Calendar]

Next Day >>