From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: netdev@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Date: Mon, 18 Dec 2006 14:00:26 +0100 [thread overview]
Message-ID: <458690EA.2000405@ciphirelabs.com> (raw)
In-Reply-To: <20061218095740.GA5219@2ka.mipt.ru>
Evgeniy Polyakov wrote:
> Actually I do not recall what is 'size retrictions' - if you talk about
> possibility to use software crypto provider, which supports one cipher
> in a time, then yes, but it is intended to be used with hardware though.
> Otherwise I do not recall any problems pointed to me.
sorry, "size restriction" was the wrong term. acrypto only supports
"sync provider only supports AES-128 in CBC mode, so if you try
different ciphers, there can be some problems."
and I'm using dm-crypto with aes-cbc-essiv:sha256 and your acrypto patch
breaks this setup - not only acrypto doesn't provide crypto capability
for my setup, but with this patch it is not offered by the old mechanism
either, so my system has no way to decrypt the root partition. note:
that was with the 2.6.18 patch, no idea if it is different now.
so while the patch adds new features, it also removes some features -
not sure if always (via patch) or via compile option or via module
load. also I'm not sure if acrypto can be disabled via kernel command
line to get the old behaviour (including aes-cbc-essiv:sha256 support
for dm-crypt).
would be nice to track those issues, so people testing your patch
are aware of the situation.
Regards, Andreas
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Jellinghaus <aj@ciphirelabs.com>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, netdev@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANN] Acrypto asynchronous crypto layer 2.6.19 release.
Date: Mon, 18 Dec 2006 14:00:26 +0100 [thread overview]
Message-ID: <458690EA.2000405@ciphirelabs.com> (raw)
In-Reply-To: <20061218095740.GA5219@2ka.mipt.ru>
Evgeniy Polyakov wrote:
> Actually I do not recall what is 'size retrictions' - if you talk about
> possibility to use software crypto provider, which supports one cipher
> in a time, then yes, but it is intended to be used with hardware though.
> Otherwise I do not recall any problems pointed to me.
sorry, "size restriction" was the wrong term. acrypto only supports
"sync provider only supports AES-128 in CBC mode, so if you try
different ciphers, there can be some problems."
and I'm using dm-crypto with aes-cbc-essiv:sha256 and your acrypto patch
breaks this setup - not only acrypto doesn't provide crypto capability
for my setup, but with this patch it is not offered by the old mechanism
either, so my system has no way to decrypt the root partition. note:
that was with the 2.6.18 patch, no idea if it is different now.
so while the patch adds new features, it also removes some features -
not sure if always (via patch) or via compile option or via module
load. also I'm not sure if acrypto can be disabled via kernel command
line to get the old behaviour (including aes-cbc-essiv:sha256 support
for dm-crypt).
would be nice to track those issues, so people testing your patch
are aware of the situation.
Regards, Andreas
next prev parent reply other threads:[~2006-12-18 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 19:15 [ANN] Acrypto asynchronous crypto layer 2.6.19 release Evgeniy Polyakov
2006-12-18 7:38 ` Andreas Jellinghaus
2006-12-18 7:38 ` Andreas Jellinghaus
2006-12-18 9:57 ` Evgeniy Polyakov
2006-12-18 13:00 ` Andreas Jellinghaus [this message]
2006-12-18 13:00 ` Andreas Jellinghaus
2006-12-18 13:13 ` Evgeniy Polyakov
2006-12-19 10:51 ` Andreas Jellinghaus
2006-12-19 10:59 ` Evgeniy Polyakov
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=458690EA.2000405@ciphirelabs.com \
--to=aj@ciphirelabs.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.