Re: xen_4.1.6.1-1+deb7u2.dsc
Bastian Blank writes: > Here you go: > > https://korte.credativ.com/~bbl/xen/xen_4.1.6.lts1~e98efe58-1.dsc Thanks. I don't have time right now, however will look at this early next week. -- Brian May
July Report
In June 2017, my 5th month as a debian-lts contributor, I was allocated 14.7 hours and I used all the 14.7 hours. In this time I did the following: * Reviewed changes for xen. * Updated and released security update for pidgin. Fixed: CVE-2016-2365 CVE-2016-2366 CVE-2016-2367 CVE-2016-2368 CVE-2016-2369 CVE-2016-2370 CVE-2016-2371 CVE-2016-2372 CVE-2016-2373 CVE-2016-2374 CVE-2016-2375 CVE-2016-2376 CVE-2016-2377 CVE-2016-2378 CVE-2016-2380 CVE-2016-4323 * Updated and released binutils. Fixed: * CVE-2016-2226.patch: Exploitable buffer overflow * CVE-2016-4487.patch: Invalid write due to a use-after-free to array btypevec * CVE-2016-4488.patch: Invalid write due to a use-after-free to array ktypevec * CVE-2016-4489.patch: Invalid write due to integer overflow * CVE-2016-4490-1.patch: Write access violation * CVE-2016-4490-2.patch: Write access violation * CVE-2016-4492_CVE-2016-4493.patch: Read/write access violations * CVE-2016-6131.patch: Libiberty Demangler segfaults * CVE-2016-.patch: Stack buffer overflow when printing bad bytes in Intel Hex objects * Researched security fix for kde4libs. In particular CVE-2016-6232. -- Brian May
Re: xen_4.1.6.1-1+deb7u2.dsc
Hi Guido I fixed the problem with i386. Turns out it was I way too large shift. Fixed sources: https://korte.credativ.com/~bbl/xen/xen_4.1.6.lts1~f5a8dc19-1.dsc On Mon, Jul 25, 2016 at 06:57:13PM +0200, Guido Günther wrote: > Can you give us an idea what you tested and what would be needed to > get this in a DLA ready state? Will you perform the remaining tests > so we can upload the package and release the DSA? I tested on AMD hardware the following combinations: - x86-32 hypervisor, i386 system - x86-64 hypervisor, i386 system - x86-64 hypervisor, am64 system I tested a minimal PV domain with the following config: | name="test" | kernel="/boot/vmlinuz-3.2.0-4-amd64" | ramdisk="/boot/initrd.img-3.2.0-4-amd64" | on_crash="preserve" I tested HVM with a full debian 7 system. I tested migration (non-live and live) with itself: | # xen migrate --live test localhost I'm missing any test on Intel hardware. If this works I'll make a release. Regards, Bastian -- One does not thank logic. -- Sarek, "Journey to Babel", stardate 3842.4
Re: Security support for libav in Debian Wheezy
Sorry, I'm afraid I maintained too much radio silence.. On 2016-07-23 19:08, Markus Koschany wrote: I am contacting you on behalf of the Debian LTS team. Two months ago you voiced your interest in helping us to fix open security issues in libav. https://security-tracker.debian.org/tracker/source-package/libav Can you tell us more about the latest developments? If you have any questions regarding Debian LTS work, please send them to the debian-lts list and I will try to answer them in a timely manner. I got sidetracked by other work and by trying to get access to the Google ClusterFuzz samples[1]. I have access to a bunch of them now, but not the whole lot and it turns out that I don't necessarily need them in each and every case to port fixes. So yeah, that was a bit of a wild goose chase :-/ In any case I have the first set of three patches[2] queued up for pushing to the 0.8 branch. I've sent them to the libav-devel mailing list to give other devs a chance to react. I expect nobody to care about stale branches, however. Thus the ETA for the patches to hit the 0.8 branch is tomorrow evening CET or the next morning at the latest. I hope and expect to churn out a steady trickle of 1-3 backports per week going forward while not on vacation now that I have all the pieces for working with those old branches back in place. best regards, Diego [1] Things with names like "0231a17345734228011c6f35a64e4594/asan_heap-oob_1d92a72_3218_1213809a9e3affec77e4c191fdfdc0a9.mov" that go along references to Mateusz "j00ru" Jurczyk and Gynvael Coldwind. [2] One backport from the Debian package, CVE-2015-1872, CVE-2015-5479.
Re: Wheezy update of libupnp?
Hi Nick, 2016-07-19 15:35 GMT+02:00 Nick Leverton : > On Tue, Jul 19, 2016 at 08:54:18AM +0200, Chris Lamb wrote: >> Hello dear maintainer(s), >> >> the Debian LTS team would like to fix the security issues which are >> currently open in the Wheezy version of libupnp: >> https://security-tracker.debian.org/tracker/TEMP-000-867096 >> >> Would you like to take care of this yourself? > > Hi, > > Thanks very much for the headsup on this. I've a bit to do for Squeeze > at the moment and would really appreciate any help your team can provide > on LTS. If I do get enough time though I'll check in on your task > tracker as suggested. I will prepare a fix for Wheezy tomorrow. Cheers, Balint
Security update of openssh for wheezy
Hi OpenSSH Maintainers and LTS team I have prepared a security update of openssh for wheezy. For more information about the issue solved see here: https://security-tracker.debian.org/tracker/CVE-2016-6210 I have applied the same patch as in sid and it applied fine, except that I had to change a call to a clear memory function to a loop instead. This function is not available in wheezy. You can find the debdiff here: http://apt.inguza.net/wheezy-security/openssh/CVE-2016-6210.debdiff You can also find the packages that I intend to upload here: http://apt.inguza.net/wheezy-security/openssh/ I have regression tested and I could login still, and use the client too. I could not reproduce the problem good enough to tell for sure that they are solved. However they should be solved just as good as in sid and jessie. If no-one objects I will upload this package in four days, that is on Saturday. Best regards // Ola -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comFolkebogatan 26\ | o...@debian.org 654 68 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / ---
