On 2015-04-17 18:22, Martin Pitt wrote:
Hello Niels,
Niels Thykier [2015-04-17 17:55 +0200]:
Just to clarify, are we still intending to do a systemd update prior
to
Jessie with -17 and then now also a p-u (i.e. for 8.1) for ecryptfs?
That's still my intent, yes, primarily to avoid people who
Hello Niels,
Niels Thykier [2015-04-17 17:55 +0200]:
> Just to clarify, are we still intending to do a systemd update prior to
> Jessie with -17 and then now also a p-u (i.e. for 8.1) for ecryptfs?
That's still my intent, yes, primarily to avoid people who have this
set up in wheezy already (#751
On 2015-04-17 15:44, Martin Pitt wrote:
> Hello all,
>
> Cyril Brulebois [2015-04-17 14:15 +0200]:
>> I tried to follow the code path in Ubuntu, which offers this option, to
>> track down where the offset can come from; and see whether Debian was
>> affected. I didn't mean to imply that Debian pro
Hello all,
Cyril Brulebois [2015-04-17 14:15 +0200]:
> I tried to follow the code path in Ubuntu, which offers this option, to
> track down where the offset can come from; and see whether Debian was
> affected. I didn't mean to imply that Debian proposes the same option,
> as it does not.
Ah ok,
On 17/04/15 13:51, Martin Pitt wrote:
> BTW, 215-16 still didn't hit testing, so I didn't upload -17 yet. I'll
> do as soon as it migrates.
systemd| 215-16 | testing | source, amd64, arm64, armel,
armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
systemd| 215-16 |
Martin Pitt (2015-04-17):
> I just tried the current rc2 installer (netinst image/graphical) and
> it does not actually ask me whether I want to encrypt my home
> direction. It seems you got this option?
I tried to follow the code path in Ubuntu, which offers this option, to
track down where the
Martin Pitt [2015-04-16 14:53 -0500]:
> Hello Cyril,
>
> Cyril Brulebois [2015-04-16 19:40 +0200]:
> > Anyway, asking for home encryption indeed leads to swap encryption,
> > through a ecryptfs-setup-swap call, which in turn triggers:
I just tried the current rc2 installer (netinst image/graphica
On Thu, Apr 16, 2015 at 10:05:17PM +0200, Cyril Brulebois wrote:
> Martin Pitt (2015-04-16):
> > Hello Cyril,
> >
> > Cyril Brulebois [2015-04-16 19:40 +0200]:
> > > Anyway, asking for home encryption indeed leads to swap encryption,
> > > through a ecryptfs-setup-swap call, which in turn trigger
Cyril Brulebois [2015-04-16 22:05 +0200]:
> Huh? Last I checked, guided encrypted LVM just works…
Yes, that's fine -- this creates an encrypted PV which then contains
unencrypted root, swap, and home partitions. This error happens if you
don't encrypt the full disk (with cryptsetup/LUKS), but just
Hello Cyril,
Cyril Brulebois [2015-04-16 19:40 +0200]:
> Anyway, asking for home encryption indeed leads to swap encryption,
> through a ecryptfs-setup-swap call, which in turn triggers:
> |echo "cryptswap$i UUID=$uuid /dev/urandom
> swap,offset=1024,cipher=aes-xts-plain64" >> /etc/cryptt
Martin Pitt (2015-04-16):
> Hello Cyril,
>
> Cyril Brulebois [2015-04-16 19:40 +0200]:
> > Anyway, asking for home encryption indeed leads to swap encryption,
> > through a ecryptfs-setup-swap call, which in turn triggers:
> > |echo "cryptswap$i UUID=$uuid /dev/urandom
> > swap,offset=10
(Cc: debian-boot@ added.)
Martin Pitt (2015-04-16):
> Hello release team,
(With my d-i release manager hat.)
> yesterday I discovered that systemd breaks a common way of setting up
> plain cryptsetup partitions. Turns out that this has already been
> known for a while, but the impact wasn't app
12 matches
Mail list logo
