9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: petter9@bissa.eu, 9front@9front.org
Subject: Re: [9front] Booting with encrypted partitions
Date: Tue, 12 Nov 2019 12:57:32 -0800	[thread overview]
Message-ID: <B0E769F36C892538837A92242C2B2E77@eigenstate.org> (raw)
In-Reply-To: 037e9f1f-1fbd-c22d-c808-67fb4b33312e@bissa.eu

> Hi,
> 
> Got a bit tired of dropping to the shell and punching in the disk 
> decryption command on every boot.  This one:
>  > disk/cryptsetup -i /dev/sdE0/fsworm /dev/sdE0/fscache /dev/sdE0/other
> Also, one typo and the entire command must be retyped :/

If you attach patches inline, it's easier to review, and they'll still
be viewable years from now.

> So i made a change to the boot process to do that for me. Don't know if 
> something like this exist but it was anyway educational for me doing 
> this (noob) and i just thought i would share in case anyone is interested.
> 
> The change to the boot script,
> http://okturing.com/src/7221/body

>  diff -r 8f9f3ee2eacf sys/src/9/boot/bootrc
>  --- a/sys/src/9/boot/bootrc     Mon Nov 11 13:35:47 2019 -0800
>  +++ b/sys/src/9/boot/bootrc     Tue Nov 12 13:10:09 2019 +0100
>  @@ -65,6 +65,11 @@
>   mt=()
>   
>   fn main{
>  +       if(! ~ $decryptfs 0) {

This line isn't quite right -- you're checking if the content of '$decryptfs'
is 0, rather than whether the list has 0 elements. You need the '#' operator:

	if(! ~ $#decryptfs 0)

Other than that, it like it will work to me.

I'll let someone else more familiar with the boot process (cinap,
probably?) comment if there's a cleaner solution that doesn't add a
new knob. Ideally, I think we'd want:

	nobootprompt=crypt!local!/dev/sdE0/fscache

but I don't see a great way to get the args for disk/cryptsetup
out of that spec.



             reply	other threads:[~2019-11-12 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 20:57 ori [this message]
2019-11-12 21:54 cinap_lenrek
2019-11-12 23:51 ` petter9
2019-11-13  5:07 ori
2019-11-13 11:45 ` hiro
2019-11-20 12:58 ` petter9

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=B0E769F36C892538837A92242C2B2E77@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    --cc=petter9@bissa.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).