Am 11.03.2012 19:29, schrieb C. Meissa:
> C. Meissa schrieb am 11.03.2012 19:26:00:
>> Worked as expected: Any ext2-fs found at (see above setup)
>> /dev/sdb1 fails with: […]
>
> Pardon me.
> _Any_ filesystem known by blkid, not just ext2, will make cryptdisks_start
> fail with these changes, as
C. Meissa schrieb am 11.03.2012 19:26:00:
> Worked as expected: Any ext2-fs found at (see above setup)
> /dev/sdb1 fails with: […]
Pardon me.
_Any_ filesystem known by blkid, not just ext2, will make cryptdisks_start
fail with these changes, as expected.
Thanks,
Carsten
--
To UNSUBSCRIBE, ema
Hi,
Jonas Meurer schrieb am 10.03.2012 01:47:18:
> I prepared packages with the fix. It would be great if you could give
> them a try an report back. You can find the packages here:
>
> http://people.debian.org/~mejo/debian/mejo-unstable/
Worked as expected: Any ext2-fs found at (see above setup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
Am 29.01.2012 11:20, schrieb C.M.:
> Package: cryptsetup Version: 2:1.3.0-3.1 Followup-For: Bug #652497
>
> Hi, I can reproduce this error on current unstable. (But looks the
> same for stable)
>
> I believe the problem is caused by conditions
Package: cryptsetup
Version: 2:1.4.1-2
Found.
Same issue same fix as above for version 1.4.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi again,
Ubuntu seems to have a similar, maybe same, problem, too:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/474258
The conditionals mentioned are the same in
cryptsetup/2:1.1.0~rc2-1ubuntu13
as in current unstable.
C.M.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ..
Package: cryptsetup
Version: 2:1.1.3-4squeeze2
Found: 2:1.1.3-4squeeze2
Found that problem on stable, too.
C.M.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: cryptsetup
Version: 2:1.3.0-3.1
Followup-For: Bug #652497
Hi,
I can reproduce this error on current unstable.
(But looks the same for stable)
I believe the problem is caused by conditions
in /lib/cryptsetup/cryptdisks.functions
in the precheck-function do_noluks() lines 319-324
that expl
Hi,
I guess the issue you are referring to is mainly that a new block device
may become /dev/sda - maybe this could be avoided by recommending to
write a udev rules file creating a symlink /dev/swap to the right
partition by first identifying the right device? Something like:
SUBSYSTEM=="block",
Package: cryptsetup
Version: 2:1.3.0-3
Severity: important
File: cryptdisks
hi
'cryptdisks' eases the use of crypted swap partitions,
the instructions in /usr/share/doc/cryptsetup/README.Debian.gz
are very easy; but there is an intrinsic danger.
Indeed, if there is a line such as
cswap1
10 matches
Mail list logo
