From: John Lane
Patch modified to take into account a change to context
brought about by c93d3e694713b8230fa2cf88414fabe005b56782
grub-core/disk/cryptodisk.c
142c142
---
grub-core/disk/cryptodisk.c | 298 +++-
grub-core/disk/l
>Am I correct in stating that your patches would only require:
>- command line options on each invocation of grub-install to reference a
>config file of sorts - a config file in a dedicated directory that would allow
>this config to persist
Xen, yes you are correct. The config file (${prefix}/e
>I would personally assume that something could be done in the dedicated
>/etc/grub.d/ directories that would allow grub-mkconfig to function as
>required without changing anything to it?
Xen, that is probably possible, but I chose to modify grub-mkconfig_lib.in
because that is where the origin
to mattle_opts.cfg for repeated grub-install/mkconfig attempts. Given
that having a detached header or plain dm-crypt for FDE including /boot is more
of an advanced setup do you think it would be too much to ask of the users to
do what I am saying is required at this time? I mentioned plain dm-cry
solution that integrates plain
dm-crypt/detached header into grub-install needs to work without user
intervention and provides some means to auto-detect this.
Although we already have some options that cannot be autodetected (e.g.
keys). So may be this can be relaxed.
But at the very least it needs
On 29.06.2015 16:30, John Lane wrote:
> From: John Lane
>
> ---
> grub-core/disk/cryptodisk.c | 298
> +++-
> grub-core/disk/luks.c | 195 +
> include/grub/cryptodisk.h | 8 ++
> 3 files changed, 310 insertions(+), 19
On 27.10.2015 12:15, Andrei Borzenkov wrote:
> On Tue, Oct 27, 2015 at 2:10 PM, Vladimir 'phcoder' Serbinenko
> wrote:
>> There are patches for it but they will not be integrated as plain dm-crypt
>> has no advantages compared to LUKS and cannot be configured reliably
On Thu 2015-10-29 13:46:42 -0400, christopher.to...@riseup.net wrote:
> No, since I type the line in manually every time, it is not located
> anywhere for it to be discovered and need denying. I know my system very
> well. I know if I put one USB drive into a slot, it will be named
> (USB0). If
ble to
utilize it. Why can't you just accept that?
Chris
On 2015-10-27 11:10, Vladimir 'phcoder' Serbinenko wrote:
There are patches for it but they will not be integrated as plain
dm-crypt
has no advantages compared to LUKS and cannot be configured
reliably when
device na
On 29 Oct 2015 6:24 am, wrote:
>
> Actually, plain dm-crypt has one distinct advantage to LUKS, and that is
one of plausible deniability. In some countries, you can be court-ordered
to decrypt the contents of a device if it can be proven that encrypted
contents exist. With LUKS, there
Actually, plain dm-crypt has one distinct advantage to LUKS, and that is
one of plausible deniability. In some countries, you can be
court-ordered to decrypt the contents of a device if it can be proven
that encrypted contents exist. With LUKS, there is no denying it; with
plain dm-crypt and
There are patches for it but they will not be integrated as plain dm-crypt
has no advantages compared to LUKS and cannot be configured reliably when
device names change as they have no UUID
Le 27 oct. 2015 8:20 AM, a écrit :
> Hello;
> I apologize if this question has already been asked.
On Tue, Oct 27, 2015 at 2:10 PM, Vladimir 'phcoder' Serbinenko
wrote:
> There are patches for it but they will not be integrated as plain dm-crypt
> has no advantages compared to LUKS and cannot be configured reliably when
> device names change as they have no UUID
>
Stil
Hello;
I apologize if this question has already been asked. A web search didn't
turn anything up. Are there any plans to include plain dm-crypt support
in a future version of grub?
Thank you.
Chris
___
Grub-devel mailing list
Grub-devel@gn
From: John Lane
---
grub-core/disk/cryptodisk.c | 298 +++-
grub-core/disk/luks.c | 195 +
include/grub/cryptodisk.h | 8 ++
3 files changed, 310 insertions(+), 191 deletions(-)
diff --git a/grub-core/disk/cryptodisk.
A little explanation of what the patch does; most of the code in this
patch already existed.
I extracted the in-line code from "luks.c" that creates the crypto disk
into a new cryptomount function called "grub_cryptodisk_create" that is
then used by the luks module and is also avilable to the cryp
---
grub-core/disk/cryptodisk.c | 298 +++-
grub-core/disk/luks.c | 205 +-
include/grub/cryptodisk.h | 8 ++
3 files changed, 309 insertions(+), 202 deletions(-)
diff --git a/grub-core/disk/cryptodisk.c b/grub-core/dis
17 matches
Mail list logo
