>Well, yes, it's been only two years, and ubuntu still destroys data
during installation. Maybe two years later someone we'll fix this bug.
Personally, I switched to W7, because my data are more expensive than
the MS license
Oh, OK. Only one more year have passed :D
No comments
--
You receiv
** Changed in: cryptsetup (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
** Branch linked: lp:~ubuntu-core-dev/cryptsetup/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To manage notification
** Branch linked: lp:ubuntu/cryptsetup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To manage notifications about this bug
This bug was fixed in the package cryptsetup - 2:1.4.1-2ubuntu2
---
cryptsetup (2:1.4.1-2ubuntu2) precise; urgency=low
* Split up package in cryptsetup and cryptsetup-bin. (LP: #343363).
* Do not overwrite existing filesystems when creating swap (LP: #474258).
* Add aesni module
** Changed in: cryptsetup (Debian)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To mana
Errata:
WRONG:
3. sudo mkdir -p /usr/local/lib/chk_size
SHOULD BE:
sudo mkdir -p /usr/local/lib
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous!
I have a patch and a workaround.
PATCH
==
I refactored the code to expose the bug and make it easier to test edge cases:
https://code.launchpad.net/~cezary0/cryptsetup/bugfix474258_refactored
If anyone can think of other/related issues, edge cases or useful test
cases - let me know and I'll
** Branch linked: lp:~cezary0/cryptsetup/bugfix474258_refactored
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To manage not
@Tuomas:
I agree - LVM is a cleaner solution (although at first, I thought the
lvm handling would need too much code).
Good points about linking and /dev/dm*.
@bugfix
It turns out there is an obvious bug with detecting filesystems before
running mkswap.
My take on fixing it:
https://code.launc
Another alternative (besides using a file on some fs) would be using LVM
volumes, and not resolving the related symlinks.
Then /etc/crypttab would look something like:
cryptswap1 /dev/mapper/swap-swap_1 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
where /dev/mapper/swap-swap_1 is a symlink maint
I had this continue trashing my new partition at every reboot and I
couldn't track the cause ...
One idea/workaround with the UUID:
- have cryptsetup allow only files or UUIDs instead of devices until
UUID support is in the swap filesystem, e.g.:
partition ->
"containing" ext3 fil
** Changed in: cryptsetup (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To manage not
** Bug watch added: Debian Bug tracker #652497
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652497
** Also affects: cryptsetup (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652497
Importance: Unknown
Status: Unknown
--
You received this bug notification becaus
** Also affects: cryptsetup (Ubuntu Precise)
Importance: Critical
Assignee: Ubuntu Foundations Team (ubuntu-foundations-team)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad
** Changed in: cryptsetup (Ubuntu)
Milestone: None => ubuntu-12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To mana
** Tags added: rls-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To manage notifications about this bug go to:
ht
this bug taged "Critical"
but why not fix this???
two yearsso long.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
T
** Tags added: rls-mgr-p-tracking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
Extremely dangerous! cryptswap killed my partition
To manage notifications about this bug go to
** Changed in: cryptsetup (Ubuntu)
Assignee: Surbhi Palande (csurbhi) => Ubuntu Foundations Team
(ubuntu-foundations-team)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/474258
Title:
E
LP: #584067 and LP: #710340 may be duplicates of this as well.
For the special case of cryptswap on LVM, /dev/mapper/* are stable unlike the
/dev/dm-* used at least in lucid...natty, and as such those could be considered
in addition to UUIDs.
--
You received this bug notification because you ar
I agree with Johnny's analysis here; any crypttab setup done via the
Ubuntu installer should use UUIDs, not partition names, since the latter
are not guaranteed to be stable.
I disagree with the original suggestion to check the partition type, as
I don't think that's a reliable check in general.
Well, yes, it's been only two years, and ubuntu still destroys data
during installation. Maybe two years later someone we'll fix this bug.
Personally, I switched to W7, because my data are more expensive than
the MS license
--
You received this bug notification because you are a member of Ubuntu
Hello Johnny,
Judging by the Ubuntu bug listings at
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bugs?field.status:list=NEW,
it would appear that the bug has already be reassigned to cryptsetup,
and it doesn't appear in the listing of bugs in cryptmount.
I'm still not sure there's a part
Hi there
You mentioned, this bug was assigned to the wrong package. Is there a
way to reassign the bug or should one of us open a new bug?
I agree, that this is a very serious bug. /etc/crypttab should use
UUID's in order to be shure and programs using it schould at least check
the partition type
** Tags added: dataloss
--
Extremely dangerous! cryptswap killed my partition
https://bugs.launchpad.net/bugs/474258
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
I sort-of agree with everyone here...
a) I have a 100% raid server running karmic (without cryptswap). I don't trust
automated tools on this system and always verify that /etc/fstab points to the
correct swap md partition after any significant change and before I reboot.
b) I have a laptop with h
In this case this encryption tool can at least check the size of mounted
partition. In my case, swap was 2g, and destroyed partition was 80g. I'm sure,
Ubuntu develepers will find the way to fix this bug.
"but I don't think that's any different from "mkswap" or many other
system-administration t
As a reminder - your bug report does NOT relate to the "cryptmount"
package given details in your original post.
The problem with running "swapon" with an encrypted partition is simply
that both the /etc/crypttab mechanisms, and those of other encryption
tools, perfectly reasonably regenerate the
"However, the proposed solution of checking partition-types before "mounting"
as swap does not seem to offer an effective protection against corrupting data
held on raw devices"
What's the problem to mount raw device in read-only mode, check what type the
unencrypted partition has? Any linux dis
This bug report really does not sound like it refers to the "cryptmount"
package.
Specifically, "cryptmount" does not use the /etc/crypttab file for any
purpose, nor does it include any utility called "cryptswap" (even though
if offers similar generic functionality).
More generally, it would appe
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
Extremely dangerous! cryptswap killed my partition
https://bugs.launchpad.net/bugs/474258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
32 matches
Mail list logo
