Chris Lamb pushed to branch master at Debian Security Tracker / security-tracker


Commits:
210d9dc4 by Chris Lamb at 2018-04-15T23:00:43+01:00
Revert "Reserve DLA-1346-1 for patch" - final testing revealed an 
issue.

This reverts commit 7ac470dd2d40fbb968e62ca0f494228579c40245.

- - - - -


2 changed files:

- data/DLA/list
- data/dla-needed.txt


Changes:

=====================================
data/DLA/list
=====================================
--- a/data/DLA/list
+++ b/data/DLA/list
@@ -1,6 +1,3 @@
-[15 Apr 2018] DLA-1346-1 patch - security update
-       {CVE-2018-1000156}
-       [wheezy] - patch 2.6.1-3+deb7u1
 [15 Apr 2018] DLA-1345-1 perl - security update
        {CVE-2018-6913}
        [wheezy] - perl 5.14.2-21+deb7u6


=====================================
data/dla-needed.txt
=====================================
--- a/data/dla-needed.txt
+++ b/data/dla-needed.txt
@@ -64,6 +64,12 @@ ming (Hugo Lefeuvre)
 --
 opencv
 --
+patch (Chris Lamb)
+  NOTE: 20180407: WIP patch here: 
https://gist.github.com/lamby/a168c9afbab3f9f808395da0d752fedb/raw, but a bit
+  NOTE: 20180407: of a rabbit-hole with respect all the newer "safe_" foo. I 
suspect if we can just avoid calling
+  NOTE: 20180407: make_tempfile (from src/util.c) and safe_unlink (from 
src/safe.c) then we can avoid most of this. (lamby)
+  NOTE: 20180415: Reserved DLA-1346-1 (now unreserved..) but final testing 
revealed an issue. Will fix asap. (lamby)
+--
 qemu
 --
 qemu-kvm



View it on GitLab: 
https://salsa.debian.org/security-tracker-team/security-tracker/commit/210d9dc444d9b21e3215daf0351627cef1ecabc3

---
View it on GitLab: 
https://salsa.debian.org/security-tracker-team/security-tracker/commit/210d9dc444d9b21e3215daf0351627cef1ecabc3
You're receiving this email because of your account on salsa.debian.org.
_______________________________________________
debian-security-tracker-commits mailing list
debian-security-tracker-commits@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-security-tracker-commits

Reply via email to