On Mon, Nov 19, 2007 at 01:38:41PM +0300, Evgeniy Polyakov wrote:
>
> > Users requiring chaining would then do
> >
> > crypto_alloc_blkcipher("foo", 0, CRYPTO_ALG_CIPHER_NOCHAIN)
>
> Hmm, users who want chaining will set flag _NOCHAIN :)
> I would call it something more informative...
Yes I know, I'm just trying to save a few keystrokes since most
existing algorithms will set NOCHAIN to 0 :)
In any case, we can create a wrapper for it, something like
crypto_alloc_chaining_cipher.
> I'm not sure what user will do, when it request chaining, but driver
> will set CRYPTO_ALG_CIPHER_NOCHAIN itself and return wrong/old in
> req->info?
> For IPsec it is not an issue though, but I can not say that for all.
Drivers that set CRYPTO_ALG_CIPHER_NOCHAIN won't be returned
if the user requests for a chaining cipher. This is the same
as when you request for a cipher with no fallback that the
system won't return one needing a fallback.
If you're worried about users doing chaining we could even
create a new frontend type for it. So the user would need
to allocate an object of type crypto_chncipher and use that
for operations that chain.
Cheers,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
