All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] FAQ 2.2 Scenario (1) - clarification concerning "encrypted root"
Date: Sun, 21 Jun 2020 01:53:26 +0200	[thread overview]
Message-ID: <20200620235326.GA23718@tansi.org> (raw)
In-Reply-To: <800292998.974117.1592673992765@mail.yahoo.com>

This critically depends on the initrd being non-manipulated.
Of course, you cannot use the initrd to verify a signature 
on the initrd securely ...

Regards,
Arno

On Sat, Jun 20, 2020 at 19:26:32 CEST, JT Morée wrote:
> I'm working through a setup right now and documenting at
> https://sites.google.com/site/jtmoree/knowledge-base/smart-cards-and-linux/kubuntu-20-04
> 
> I am using the smartcard to unlock root during the boot process.  this is
> done by the kernel and initrd using out of the box tools and processes. 
> 
> in this setup /boot is in the clear and I have some ideas for signing the
> kernel+initrd with the smart card, then verifying on boot.  will update
> the link if I get that working.
> 

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2020-06-20 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 20:45 [dm-crypt] FAQ 2.2 Scenario (1) - clarification concerning "encrypted root" d.eltzner
2020-06-20  6:10 ` Arno Wagner
2020-06-20  9:07   ` d.eltzner
2020-06-20  9:46     ` Arno Wagner
2020-06-20 17:26       ` JT Morée
2020-06-20 23:53         ` Arno Wagner [this message]
2020-06-21 20:20           ` moreejt
2020-06-22  7:33             ` Arno Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200620235326.GA23718@tansi.org \
    --to=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.