Re: boot problem after updating dropbear [solved -- MANUAL initrd works required]

2016-09-26 Thread Andrew McGlashan
Hi, On 27/09/16 02:24, Ben Hutchings wrote: > On Tue, 2016-09-27 at 00:56 +1000, Andrew McGlashan wrote: > I would guess that you previously modified > /usr/share/initramfs-tools/hooks/dropbear and the upgrade overwrote > your changes. That would not be a bug since it's not a configuration > file

Re: Wheezy update for qemu ?

2016-09-26 Thread Hugo Lefeuvre
Hi Guido, > The Wheezy version lacks usb_xhci_exit completely. Isn't that a much > bigger leak? Did you try to unplug/replug xhci and see if it leaks? I'm currently investigating this, but will have less time than excepted in the two next days. So, if anybody could try it, it would be helpful. >

Wheezy update for qemu ?

2016-09-26 Thread Hugo Lefeuvre
Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of qemu: https://security-tracker.debian.org/tracker/source-package/qemu Would you like to take care of this yourself? If yes, please follow the workflow we have def

Re: boot problem after updating dropbear [solved -- MANUAL initrd works required]

2016-09-26 Thread Ben Hutchings
On Tue, 2016-09-27 at 00:56 +1000, Andrew McGlashan wrote: > Hi, > > Okay, it turns out that the only files that were missing were ones that > I had in the /etc/initramfs-tools/root/ directory. > > > The only files in the faulty initrd image were from the > /etc/initramfs-tools/root/.ssh/ direct

Re: boot problem after updating dropbear [solved -- MANUAL initrd works required]

2016-09-26 Thread Andrew McGlashan
Hi, Okay, it turns out that the only files that were missing were ones that I had in the /etc/initramfs-tools/root/ directory. The only files in the faulty initrd image were from the /etc/initramfs-tools/root/.ssh/ directory, so missing .profile and other required files. I modified the initrd

Re: boot problem after updating dropbear

2016-09-26 Thread Andrew McGlashan
Hi, On 26/09/16 20:24, Chris Lamb wrote: > Andrew McGlashan wrote: > >> Before the update I could ssh to box, connecting with dropbear, and >> unlock crypt volumes, then kill the askpass process to continue the boot. >> >> After the update, the ssh session with dropbear is missing all sorts of >>

Re: boot problem after updating dropbear

2016-09-26 Thread Chris Lamb
Andrew McGlashan wrote: > Before the update I could ssh to box, connecting with dropbear, and > unlock crypt volumes, then kill the askpass process to continue the boot. > > After the update, the ssh session with dropbear is missing all sorts of > stuff; my aliases and other setup files aren't av

boot problem after updating dropbear

2016-09-26 Thread Andrew McGlashan
Hi, After dropbear update as follows: < ii dropbear 2012.55-1.3 amd64lightweight SSH2 server and client --- > ii dropbear 2012.55-1.3+deb7u1 amd64lightweight SSH2 server and client Debian Version 7.11 (Wheezy) Before th