Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2012-07-21 Thread Michael Stapelberg
Hi, This bug bit me again, so here is the next iteration of posting patches… :-( On Mon, 09 Jul 2012 21:43:09 +1200 Hugh Davenport h...@davenport.net.nz wrote: Just noting that if you add another architecture to your install then the patch from #20 will fail. Attached is a patch on top of

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2012-07-09 Thread Hugh Davenport
Package: initramfs-tools Version: 0.106 Followup-For: Bug #630581 Just noting that if you add another architecture to your install then the patch from #20 will fail. Attached is a patch on top of that. Cheers, Hugh -- Package-specific info: -- initramfs sizes -- /proc/cmdline

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2012-06-18 Thread Hugh Davenport
Package: dropbear Version: 2012.55-1 Followup-For: Bug #630581 Attached is a multiplatform patch I couldn't figure out a clean way to work out the -linux-gnu part without getting autoconf involved, so a * should be practical in most setups Cheers, Hugh -- System Information: Debian Release:

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2012-06-15 Thread Thomas Mueller
Package: dropbear Version: 2012.55-1 hi could not login into the initramfs to unlock the encrypted root drive. the password-less authentication always failed. Patch from comment #20 fixes the password-less login problem for me. - Thomas -- To UNSUBSCRIBE, email to

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2012-03-17 Thread Florian Streibelt
I'm using dropbear 0.52-5 on amd64 arch. The bug is still here and solution from message #20 does not work for me. for me it seems /lib/libnsl.so.1 /lib/libnsl-2.11.3.so are missing, so I added copy_exec /lib/libnsl.so.1 /lib/ copy_exec /lib/libnsl-2.11.3.so /lib/ /florian -- To

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2012-01-19 Thread Fredrik Olofsson
This just bit me again, my local changes to the hook had been overwritten. Are there any issues using dpkg to find which files to copy? Why not just change it and be gone with this bug? cp $(dpkg -L libc6 | grep libnss_ | tr '\n' ' ') ${DESTDIR}/lib/ (For some reason I wasn't subscribed to the

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2011-11-16 Thread Gerrit Pape
Hi Chris, I just uploaded a new upstream version of dropbear. There're currently some bugs open concerning the initramfs integration, if you have any changes to the dropbear package to suggest, I'd be happy to swiftly review and integrate them into a subsequent upload. See #584780, #630581,

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2011-11-06 Thread Alex Roper
Since afaict this hasn't been fixed upstream, and it just cost me half an hour /again/, here is Michael's fix in its own hook for convenience. Just put this into /etc/initramfs-tools/hooks and run update-initramfs -u This way we don't have to modify apt-managed initramfs files while waiting for

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2011-09-02 Thread Michael Stapelberg
Hi, attached is a patch which works on all architectures. It uses dpkg -L to list the contents of libc6 (containing the libnss* files) because that seems to be the easiest way to work around having to get the multi-arch triplet (x86_64-linux-gnu). Best regards, Michael dropbear.patch

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2011-07-19 Thread Alex Roper
Confirmed on amd64, though obviously the patch for that will need to be a bit different. I wondered why my servers didn't boot today and this seems to be why:-) Relevant keyword for people Googling this bug: dropbear dbclient Unknown own user On a related note, looking at the dropbear source I'm

Bug#630581: dropbear: Initramfs hook uses wrong path to libnss_*

2011-06-15 Thread Fredrik Olofsson
Package: dropbear Version: 0.53.1-1 Severity: important The initramfs hook fails to copy libnss_* to the initramfs image. In my case, this makes my server unbootable since I need to login using ssh to unlock the root file system (reason for important). Updating