Hi Guilhem,
Am 24.12.2015 um 20:57 schrieb Guilhem Moulin:
> On Wed, 23 Dec 2015 at 23:11:29 +0100, Jonas Meurer wrote:
>> Guilhem, can you test the latest SVN version and verify that it works fo
>> you?
>
> It works great, thanks! Here is another patch to
> - add an entry in d/copyright;
> -
Hi Jonas,
On Wed, 23 Dec 2015 at 23:11:29 +0100, Jonas Meurer wrote:
> Guilhem, can you test the latest SVN version and verify that it works fo
> you?
It works great, thanks! Here is another patch to
- add an entry in d/copyright;
- change cryptroot-unlock's license from GPL3+ to GPL2+ to
On Wed, 2015-12-23 at 23:19 +0100, Jonas Meurer wrote:
> Hi Ben,
>
> a quick question to you as initramfs-tools maintainer: are you ok with
> us adding a directory '/usr/share/initramfs-tools/bin' to the cryptsetup
> package? We would like to place a script 'cryptroot-unlock' there which
> is
Hi Ben,
a quick question to you as initramfs-tools maintainer: are you ok with
us adding a directory '/usr/share/initramfs-tools/bin' to the cryptsetup
package? We would like to place a script 'cryptroot-unlock' there which
is installed into /bin/ in initramfs. Thus the directory
Am 19.12.2015 um 18:50 schrieb Guilhem Moulin:
> On Fri, 18 Dec 2015 at 19:16:56 -0500, Richard Hansen wrote:
>> * why SIGKILL instead of SIGTERM? seems too aggressive
>> * perhaps add a waitpid() after the kill() to ensure that a second
>>plymouth won't be run before the first one exits
>
On Fri, 18 Dec 2015 at 19:16:56 -0500, Richard Hansen wrote:
> * why SIGKILL instead of SIGTERM? seems too aggressive
> * perhaps add a waitpid() after the kill() to ensure that a second
>plymouth won't be run before the first one exits
Agreed, but unfortunately plymouth doesn't terminate
On Wed, 16 Dec 2015 at 23:37:31 -0500, Richard Hansen wrote:
> It should work on Debian, though I have not tested it.
The client part can't be shipped by cryptsetup; instead, it should have
its own ‘dropbear-initramfs-client’ package. But IMHO this is not
really necessary: as explained in
Apologies, I forgot to say that the script I linked is meant to be a
temporary workaround until proper remote unlocking support is added. I
posted it as a reference for those who stumble across this bug report
looking for a way to get remote unlocking to work right away.
Regarding the original
This is the script I use to remotely unlock an encrypted root filesystem
on my Ubuntu machines:
https://github.com/rhansen/unlock-cryptroot
It should work on Debian, though I have not tested it.
It does not require any modifications to the target system's initramfs,
and works even if
On Thu, 01 Oct 2015 at 12:24:58 +0200, Guilhem Moulin wrote:
> since I like Matthias' solution better
On second thought I take that back on second thought. Aside from a typo
in my previous patch, init scripts such as /scripts/local-top/cryptroot
are intended to run sequentially, and running two
Hi there,
As a dropbear (in particular its remote unlocking feature) co-maintainer (see
#790125) I'd like to support this :-)
This bug has just been brought to my attention and it convinced me not
to make dropbear-initramfs conflict with plymouth. Solving the problem
at the root seems like the
Package: cryptsetup
Version: 2:1.4.3-4
Severity: important
Tags: patch
Dear Maintainer,
The cryptroot script always uses plymouth if present (plymouth is
installed by default on Ubuntu).
Unfortunately this prevents to unlock an encrypted root from console
(e.g. via SSH).
Attached is a patch with
12 matches
Mail list logo
