Using UUID in crypttab brought a regression, known as bug #1303002 and
bug #1310058 (there may be more duplicates).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172014
Title:
encrypted swap
This bug was fixed in the package ecryptfs-utils - 104-0ubuntu1
---
ecryptfs-utils (104-0ubuntu1) trusty; urgency=low
[ Colin King ]
* src/libecryptfs/ecryptfs-stat.c, tests/kernel/extend-file-
random/test.c, tests/kernel/inode-race-stat/test.c,
** Branch linked: lp:~ubuntu-branches/ubuntu/trusty/ecryptfs-utils
/trusty-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172014
Title:
encrypted swap device not correctly configured on
Also, as my knowledge of cryptsetup is slim, I tried and failed to find
out the UUID for my encrypted swap
cthufoo@ryleh:/etc$ sudo tune2fs -l /dev/sdb3
tune2fs 1.42.8 (20-Jun-2013)
tune2fs: Bad magic number in super-block while trying to open /dev/sdb3
Couldn't find valid filesystem superblock.
Installed Saucy and have same issue
My understanding is that having a random key for the partition resets
the UUID to something new on each boot. Making the only available fixes:
randomly do without swap, use a password key for swap, or leave swap
unencrypted.
--
You received this bug
=== modified file 'src/utils/ecryptfs-setup-swap'
--- src/utils/ecryptfs-setup-swap 2012-04-18 16:11:37 +
+++ src/utils/ecryptfs-setup-swap 2013-05-08 18:53:53 +
@@ -161,7 +161,7 @@
[ -e /dev/mapper/cryptswap$i ] || break
done
# Add crypttab
** Branch linked: lp:ecryptfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172014
Title:
encrypted swap device not correctly configured on fresh raring install
To manage notifications about this
Committed revision 776.
** Changed in: ecryptfs-utils (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172014
Title:
encrypted swap device not
It's meant to write UUIDs.
James, could we please have installer logs for this?
** Package changed: ubiquity (Ubuntu) = partman-crypto (Ubuntu)
** Changed in: partman-crypto (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Wait, swap - I misread. ecryptfs-setup-swap looks up the UUID but
doesn't write it out in crypttab. That seems like a bug there.
** Package changed: partman-crypto (Ubuntu) = ecryptfs-utils (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And in fact it'd need to look up the LUKS UUID anyway in order to write
it to crypttab. Compare partman-crypto:
# Use UUID for LUKS devices
if cryptsetup isLuks $source; then
local uuid=$(cryptsetup luksUUID $source)
source=UUID=$uuid
fi
Assuming my analysis is correct, this is not a regression: it dates back
at least to precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1172014
Title:
encrypted swap device not correctly
The setup of /etc/crypttab comes from the installer, not from
cryptsetup; reassigning.
Dmitrijs, does this issue sound familiar to you?
** Package changed: cryptsetup (Ubuntu) = ubiquity (Ubuntu)
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) = Dmitrijs Ledkovs (xnox)
--
You
13 matches
Mail list logo
