From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [ACRYPTO] New asynchronous crypto layer (acrypto) release.
Date: Thu, 19 Oct 2006 17:04:19 +0200 [thread overview]
Message-ID: <453793F3.1080207@ciphirelabs.com> (raw)
In-Reply-To: <20060929094809.GA31117@2ka.mipt.ru>
Hi,
I finally got around testing 2.6.18.1 + acrypto.
but it "does not work" - I usualy boot, enter my
passphrases for rsa key / openssl decrypts some random
bytes with them, and a hex version of those random bytes
is used with dm-setup to initialize a dm-crypt mapping
which again is used for mounting root and swap (or
resume in case it has a suspend image on them).
but with the acrypto patched kernel the system freezes
without any response. the script in the initramfs is not
"set +x" so I'm not sure which command causes the freeze,
so I guess it is either the dm-setup, the resume trigger
(echo to a file in /sys/) or the mount for root or the
swapon.
> As I answered in your first e-mail, yes, you just need to patch 2.6.18
> tree and load one of the crypto provider.
what exactly would be "load one of the crypto providers"?
+# Asynchronous crypto layer
+#
+CONFIG_ACRYPTO=y
+CONFIG_ASYNC_PROVIDER=y
+# CONFIG_CONSUMER is not set
+# CONFIG_ASYNC2OCF_BRIDGE is not set
+
+#
this change to .config should be enough
(ok, 2.6.18.1 also enabled CONFIG_CONNECTOR and CONFIG_PROC_EVENTS).
I documented the setup of my laptop with encryption here:
https://help.ubuntu.com/community/EncryptedFilesystemHowto4
and I can post kernel config etc. if it helps. there was no
kernel message when the machine froze (or more like waiting
for something forever - ctrl-alt-del still worked fine).
note: kernel 2.6.18 was working fine, I didn't try 2.6.18.1
without acrypto changes, but I guess that isn't the issues.
still if you think otherwise, I can give it a try. if there
is some boot option to disable acrypto so dm-crypt will work
as if compiled without acrypto, I would try that too.
is there such an option?
Thanks, Andreas
next prev parent reply other threads:[~2006-10-19 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 12:08 [ACRYPTO] New asynchronous crypto layer (acrypto) release Evgeniy Polyakov
2006-09-28 13:23 ` Andreas Jellinghaus
2006-09-28 13:35 ` Evgeniy Polyakov
2006-09-29 9:48 ` Evgeniy Polyakov
2006-10-19 15:04 ` Andreas Jellinghaus [this message]
2006-10-20 6:31 ` Evgeniy Polyakov
2006-10-20 13:34 ` Andreas Jellinghaus
2006-10-21 6:59 ` Evgeniy Polyakov
2006-09-29 10:17 ` Samuel Tardieu
2006-09-29 10:51 ` Evgeniy Polyakov
2006-09-29 17:31 ` Vincent Jardin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453793F3.1080207@ciphirelabs.com \
--to=aj@ciphirelabs.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox