On 05/30/2016 09:05 PM, Brian Santich wrote:


On Monday, May 30, 2016 at 8:35:25 PM UTC-4, Chris Laprise wrote:



    On 05/30/2016 06:46 PM, [email protected] wrote:
    > Hello,
    >
    > I am trying to mount several encrypted (LUKS) internal HDDs into
    one of several AppVMs. Currently, I can attach the drive via the
    manager, followed by mounting it via password/mount commands but I
    was hoping to automate the process more. Is there a way I have
    auto-mounting in dom0 simplify the process for me? For example, if
    I add a crypttab/fstab entry, can I have attach the unencrypted
    drive in my AppVM, instead of the encrypted device?
    >
    > Having to decrypt and mount each drive each time in each AppVM
    is somewhat laborious and I was hoping there would be a more
    straightforward approach.
    >
    > Thanks
    >
    > Brian
    >

    I would search for examples of adding external drives to crypttab and
    fstab, then set it up for that particular vm using
    /rw/config/rc.local.

    Chris


Hi Chris,

How do I give this VM access to the drive in question, before it starts up (and runs the custom script)? If I write a normal script to mount/decrypt the it doesnt work, in part, because it doesnt have access to the disk yet, which I can attach only after it has started up.

Brian


You could add a udev rule to dom0 that executes a 'qvm-block -a' command to attach the drive to the vm. Actually, this rule could do all the work: After qvm-block, use qvm-run to send the cryptsetup and mount commands to the vm. Probably you don't need crypttab.

Chris

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/574CEE23.6000307%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.

Reply via email to