Processed: user debian-secur...@lists.debian.org ..., usertagging 729573

Processing commands for cont...@bugs.debian.org: > user debian-secur...@lists.debian.org Setting user to debian-secur...@lists.debian.org (was car...@debian.org). > retitle 729573 linux-image-3.2.0-4-amd64: CVE-2013-4579: [ath9k_htc] MAC > address not properly updated Bug #729573 [src:linux] linu

linux-latest_54_i386.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 13 Nov 2013 03:30:59 + Source: linux-latest Binary: linux-source linux-doc linux-tools linux-image-alpha-generic linux-headers-alpha-generic linux-image-alpha-smp linux-headers-alpha-smp linux-image-alpha-leg

Processing of linux-latest_54_i386.changes

linux-latest_54_i386.changes uploaded successfully to localhost along with the files: linux-latest_54.dsc linux-latest_54.tar.gz linux-doc_3.11+54_all.deb linux-source_3.11+54_all.deb linux-tools_3.11+54_all.deb linux-image-486_3.11+54_i386.deb linux-headers-486_3.11+54_i386.deb lin

[PATCH] deb-pkg: Inhibit initramfs builders if CONFIG_BLK_DEV_INITRD is not set

The kernel postinst hook for initramfs-tools will build an initramfs on installation unless $INITRD is set to 'No'. make-kpkg generates a postinst script that sets this variable appropriately, but we don't. Set it based on CONFIG_BLK_DEV_INITRD. This should also work with dracut when

Bug#728392: linux: Please update m68k config

On Thu, 2013-11-14 at 17:38 +, Thorsten Glaser wrote: > Dixi quod… > > >Ben Hutchings dixit: > > > >>> One’s to add back CONFIG_BRK which is apparently needed to run a > >>> popular ramdisk image used e.g. when testing the hardware or setting > >>> up a completely new system. > >> > >>You mean

Bug#729573: linux-image-3.2.0-4-amd64: [ath9k_htc] MAC address not properly updated

On Thu, Nov 14, 2013 at 02:41:32PM +0100, Mathy Vanhoef wrote: > Can a CVE ID be assigned to this? You have to refer to oss-secur...@lists.openwall.com. Debian can only assign CVE for non-public issues. Bastian -- The heart is not a logical organ. -- Dr. Janet Wallace, "The Dea

Bug#729600: linux-image-3.2.0-4-amd64: System hang upon formatting dm-crypt volume

Package: src:linux Version: 3.2.51-1 Severity: important Dear Maintainer, I'm trying to use cryptsetup to create a loopback encrypted disk volume. Here's approximately what I did: # dd if=/dev/urandom of=main.disk bs=1M count=1 # cryptsetup -y -v luksFormat --cipher aes-xts-plain64 -s 51

Bug#728392: linux: Please update m68k config

Dixi quod… >Ben Hutchings dixit: > >>> One’s to add back CONFIG_BRK which is apparently needed to run a >>> popular ramdisk image used e.g. when testing the hardware or setting >>> up a completely new system. >> >>You mean CONFIG_COMPAT_BRK. I don't like this but I doubt anyone cares >>to write e

Bug#729567: When a large TCP segment (created by generic-receive-offload) is split up who is supposed to create the checksums?

So this is what I think is happening. My router machine, running 3.10, has generic-receive-offload set on its LAN port. It happily sticks together five 1354 byte segments to make one nice tasty 6670 byte segment. Which then gets routed to a tun device, going to OpenVPN, so the fat 6670 byt

Processing of linux_3.11.8-1_multi.changes

linux_3.11.8-1_multi.changes uploaded successfully to localhost along with the files: linux_3.11.8-1.dsc linux_3.11.8.orig.tar.xz linux_3.11.8-1.debian.tar.xz linux-support-3.11-2_3.11.8-1_all.deb linux-doc-3.11_3.11.8-1_all.deb linux-manual-3.11_3.11.8-1_all.deb linux-source-3.11_3.1

Bug#723177: linux-image-3.10-3-kirkwood: please build with CONFIG_MARVELL_PHY=m

On Mon, 2013-11-11 at 11:37 -0800, Martin Michlmayr wrote: > Unfortunately I cannot remember (and I cannot even read the commit > messages right now because Alioth is done). git svn tells me that r14178 was the following. commit a3535d328fe523c7c3dd0db212ee4f34d2c40583 Author: tbm Date: Sun Au

Bug#729567: Acknowledgement (linux-image-3.10-0.bpo.3-amd64: Forwarding TCP from one LAN to another via an OpenVPN tunnel is extremely slow)

Looking at the traces in more detail "-vv" I see on the receiving system: 11:59:23.025658 IP (tos 0x8, ttl 62, id 42831, offset 0, flags [DF], proto TCP (6), length 1406) caronia.CalvaEDI.COM.33232 > olympic.calvaedi.com.ssh: Flags [.], cksum 0x1003 (incorrect -> 0xb1b9), seq 3073:4427

Bug#729573: linux-image-3.2.0-4-amd64: [ath9k_htc] MAC address not properly updated

Package: src:linux Version: 3.2.51-1 Severity: normal Tags: security upstream Dear Maintainer, I found a bug in the ath9k_htc driver for Atheros WiFi dongles. When a user changes their MAC address, an attacker can retrieve the original MAC address, which is a potential privacy risk. Details of

Bug#726676: Maybe this has some connection to bug 729567

But my problem seems to have nothing to do with ARP. Do my traces look like yours? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5284c379.2040...@atlantech.com

Bug#727736: Latest linux-image-686-pae fail to boot a xen domU

On Mon, 2013-11-04 at 03:36 +, Ben Hutchings wrote: > OK, please can someone provide text for this? Note it will need to go > in the meta-packages built by linux-latest, not the kernel image > packages themselves, because apt-showchanges never shows NEWS for a > new binary package. Not sure i

Processed: Re: Bug#729542: firmware-ipw2200: instability with firmware 3.1

Processing control commands: > reassign -1 firmware-ipw2x00 0.36+wheezy.1 Bug #729542 [firmware-ipw2200] firmware-ipw2200: instability with firmware 3.1 Warning: Unknown package 'firmware-ipw2200' Bug reassigned from package 'firmware-ipw2200' to 'firmware-ipw2x00'. No longer marked as found in ve

Re: Bug#729542: firmware-ipw2200: instability with firmware 3.1

Control: reassign -1 firmware-ipw2x00 0.36+wheezy.1 On Mi, 13 nov 13, 18:44:36, Andres Salomon wrote: > Package: firmware-ipw2200 > Version: 0.36+wheezy.1 > > On my thinkpad x40, after a full day of use the wireless stops > functioning. This is with the ipw2200 3.1 firmware, which is currently >