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
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
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
(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
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.o
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #781604 (http://bugs.debian.org/781604)
# Bug title: `journalctl /dev/sda` shows empty
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello release team,
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
Hello release team,
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 appreciated enough:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751707
What happens is that
Package: release-notes
Tags: jessie
Hi,
having both logind and acpid handle ACPI events can lead to undesired
results, esp. with a non-default configuration. As an example, logind
could try to shutdown the system on a power button press (default), but
acpid was manually configured to just suspend
Processing commands for cont...@bugs.debian.org:
> severity 751707 critical
Bug #751707 [systemd] systemd: offset is ignored in /etc/crypttab
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
751707: http://bugs.debian.org/cg
Processing commands for cont...@bugs.debian.org:
> tags 751707 + pending
Bug #751707 [systemd] systemd: offset is ignored in /etc/crypttab
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
751707: http://bugs.debian.org/cgi-bin/bugreport.cgi?bu
Control: severity -1 critial
Hello,
Stuart Pook [2014-06-15 20:34 +0200]:
> My /etc/crypttab contains
>
> swap_raw /dev/disk/by-uuid/1e0707ec-4420-49b7-96db-b3a5e72325be /dev/urandom
> swap,cipher=aes-cbc-essiv:sha256,size=128,hash=sha256,offset=4096
>
> and this worked fine with cryptdisks_st
On Thu, Apr 16, 2015 at 10:36:32 +0100, Ian Campbell wrote:
> On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote:
> > But I did have one occasion where one out of my 3 qnaps repeatedly failed
> > to
> > boot after the latest kernel update (or at least the latest flash-kernel
> > trigger, maybe it
On Thu, 2015-04-16 at 11:28 +0200, reportbug wrote:
> On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote:
> > BTW, when this fails the system still booted and you could login and fix
> > it, i.e. it didn't stall the boot or anything, is that right? If that is
> > the case a release note mig
On Thu, Apr 16, 2015 at 10:21:06 +0100, Ian Campbell wrote:
> BTW, when this fails the system still booted and you could login and fix
> it, i.e. it didn't stall the boot or anything, is that right? If that is
> the case a release note might be the most plausible action at this
> point.
When I saw
On Thu, 2015-04-16 at 10:28 +0200, reportbug wrote:
> On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote:
> > @reportbug (sorry I don't seem to know your real name), could you try
> > adding a call to "udev settle" to the qcontrold initscript, in the start
> > case right before the daemon i
On Wed, Apr 15, 2015 at 19:19:24 +0100, Ian Campbell wrote:
> @reportbug (sorry I don't seem to know your real name), could you try
> adding a call to "udev settle" to the qcontrold initscript, in the start
> case right before the daemon is launched (I can be more specific if you
> need).
Hi. It p
18 matches
Mail list logo
