mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: "Jan Lübbe" <jlu@pengutronix.de>
To: Brian Hutchinson <b.hutchman@gmail.com>, rauc@pengutronix.de
Subject: Re: [RAUC] Stumped, have a appfs partition that is encrypted, how to get RAUC to update it
Date: Thu, 22 Jul 2021 14:16:48 +0200	[thread overview]
Message-ID: <d3997af0a43d807c088e08123c6591da071fc1ba.camel@pengutronix.de> (raw)
In-Reply-To: <CAFZh4h-Azk-qGZPt1wEhqOLDtvhvTXc0Gn5pvo4y1v5=tx=XWQ@mail.gmail.com>

On Thu, 2021-07-22 at 08:11 -0400, Brian Hutchinson wrote:
> Hello again,

Hi!

> I'm wanting to have a rootfs that is read-only SquashFS and a appfs that is
> encrypted.

I assume you want to have a A/B appfs.

How do you encrypt your appfs? dm-crypt or fscrypt?

> And I'm kind of stumped.  I've searched the Documentation and archives and it
> doesn't look like RAUC has native support for encrypted partitions but in the
> archives I saw where one gentleman needed to create encrypted bundles so this
> might be similar to my problem.

Bundle encryption is independent of encryption in the rest of the system.

> I know a bundle can have pre and post triggers so maybe I can use those to
> cryptsetup luksOpen the partition and then mount it and then RAUC can do it's
> normal thing ... but I've not researched that enough to know if that's the way
> to go so thought I'd ask for some guidance to point me in the right direction
> first.

If you use dm-crypt, you can just use the device-mapper path for the slot's
device= propert in system.conf. That way, the encryption is transparent to rauc.

Regards,
Jna
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


_______________________________________________
RAUC mailing list

  reply	other threads:[~2021-07-22 12:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 12:11 Brian Hutchinson
2021-07-22 12:16 ` Jan Lübbe [this message]
     [not found]   ` <CAFZh4h8Hd+sBBNz9m1ZJvnHEg9hsL4R19cmKJ21Y9Asiss2B5Q@mail.gmail.com>
2021-07-23 12:45     ` Brian Hutchinson
2021-07-23 13:40     ` Jan Lübbe
2021-07-30 13:33       ` Brian Hutchinson
2021-07-30 14:20         ` Brian Hutchinson
2021-07-30 16:29           ` Jan Lübbe
2021-08-02 15:22             ` Brian Hutchinson
2021-08-02 15:39               ` Jan Lübbe

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=d3997af0a43d807c088e08123c6591da071fc1ba.camel@pengutronix.de \
    --to=jlu@pengutronix.de \
    --cc=b.hutchman@gmail.com \
    --cc=rauc@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox