Re: udisksctl unlock parameter for keyfiles

2012-09-11 Thread Martin Pitt
Hello Sebastian, Sebastian Fischmeister [2012-09-11 15:17 -0400]: > Cryptsetup requires root access and I don't want that for my backup > mechanism. Also I don't want to call sudo in a cron job. Sounds like you should give the backup user the org.freedesktop.udisks2.encrypted-unlock privilege for

Re: udisksctl unlock parameter for keyfiles

2012-09-11 Thread Sebastian Fischmeister
Cryptsetup requires root access and I don't want that for my backup mechanism. Also I don't want to call sudo in a cron job. The encrypted drive should be mountable by a regular user (e.g., automounting an encrypted usb stick every 10 min and copy something onto it; I don't want to keep the stick m

Re: udisksctl unlock parameter for keyfiles

2012-09-11 Thread David Zeuthen
Hi, On Tue, Sep 11, 2012 at 12:05 PM, Sebastian Fischmeister wrote: > This means one cannot script mounting an encrypted drive with > udiskctl. Is there a way around it? Is there any reason you're not just using cryptsetup(8) for this? With the way it's supposed to work, udisksctl isn't really

udisksctl unlock parameter for keyfiles

2012-09-11 Thread Sebastian Fischmeister
Hi, Is there a way to pass the keyfile to the udiskctl unlock command? It doesn't seems so, because handle_command_unlock_lock() always asks for a passphrase in udisksctl.c:1248 This means one cannot script mounting an encrypted drive with udiskctl. Is there a way around it? Thanks, Sebastian