Blacklisting (as well as assigning sha256 alias to sha256_generic) works
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko): No such
device
http
Add the line:
alias sha256 sha256_generic
to /etc/modprobe.d/aliases
This leads to the old (pre-hardy) behaviour, where sha256 is an alias for
sha256_generic and not for padlock-sha
In Gutsy, sha256 was an alias for sha256_generic
--
Warning during boot: WARNING: Error inserting padlock_sha
(/l
Workaround:
alias sha256 to sha256_generic
padlock-sha is for using the crypto-chip on via epia boards
The problem is:
padlock-sha is aliased to sha256 in hardy.
--
Warning during boot: WARNING: Error inserting padlock_sha
(/lib/modules/2.6.24/12-generic/kernel/drivers/crypto/padlock-sha-.ko):
Yes it does.
It was added to svn when I filed this bug, 0.40 was released a short time
afterwards.
--
VPNC now has rekeying support
https://launchpad.net/bugs/85504
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: vpnc
Vpnc now has rekeying support in svn. Runs without problems here. Please
update the package, as rekeying is very important in some environments.
** Affects: vpnc (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
VPNC now has reke
I have the same problems with a normal disk (/dev/hda1) as cryptroot.
Introducing a "sleep 5" let me boot my system.
# Make sure the cryptsource device is available
if [ ! -e $cryptsource ]; then
activate_vg $cryptsource
fi
+ if [ ! -e $cryptsource ];
Using feisty with cryptsetup 2:1.0.4+svn26-1ubuntu1 I still don't get a proper
password prompt. Usplash is terminated correctly but the console isn't
switched. If I switch it manually, I can't enter the password anymore. (I can
write but all I write is shown in plain text).
Which means I have to
