On Tue, 2017-11-14 at 20:05 +0100, segfault wrote:
> Vratislav Podzimek:
> > On Mon, 2017-11-13 at 17:36 +0100, segfault wrote:
> > [...]
> > > I forgot to add: Assuming that you would like to have this in upstream,
> > > some heads up for when it would be ideal for us if an upstream
> > > maintain
Vratislav Podzimek:
> On Tue, 2017-11-14 at 17:36 +0900, Kai Lüke wrote:
> [...]
>> * GNOME Disks and GIO/GVFs need to make use of the keyfiles parameter in
>> UDisks (currently lacking for LUKS as well) and a way to select a
>> keyfile from GNOME Shell is needed. One could also decide to explicitl
Vratislav Podzimek:
> On Mon, 2017-11-13 at 17:36 +0100, segfault wrote:
> [...]
>> I forgot to add: Assuming that you would like to have this in upstream,
>> some heads up for when it would be ideal for us if an upstream
>> maintainer was available for reviewing:
>> - We will evaluate the results
Hi,
thanks for the quick reply! I re-add the tails-dev mailinglist to Cc.
Kai Lüke:
> Seems I misunderstood while reading, so you already have code.
Correct. Sorry if I didn't make that clear enough. I will still answer
your previous email below. In case you already want to have a look at
the cu
On Tue, 2017-11-14 at 17:36 +0900, Kai Lüke wrote:
> Hello,
>
> of course there is more than one way to do it, but this is how I quickly
> thought about this:
>
> * use the cryptsetup support for locking/unlocking in libblockdev and
> make it work from the UDisks2.Encrypted interface
> * add the
On Mon, 2017-11-13 at 17:36 +0100, segfault wrote:
> segfault:
> > Hi,
> >
> > we at Tails (tails.boum.org) currently work on integrating support for
> > unlocking VeraCrypt (and probably also TrueCrypt) volumes in Tails via
> > udisks2 and GNOME Disks (and maybe also GNOME Files and the GVfs
> >
Seems I misunderstood while reading, so you already have code.
If your way of identifying encrypted partitions works good enough (which
is funny because the partition is not really hidden then) you can ignore
my sentences on presenting those device contents.
From the GNOME Disks point of view it wo
Hello,
of course there is more than one way to do it, but this is how I quickly
thought about this:
* use the cryptsetup support for locking/unlocking in libblockdev and
make it work from the UDisks2.Encrypted interface
* add the UDisks2.Encrypted interface in UDisks if the block device
content c
