Re: IV copy strategy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 19, 2007 at 07:56:55PM +0800, Herbert Xu (herbert@xxxxxxxxxxxxxxxxxxx) wrote:
> > 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.

Well, this looks like a good way forward.
Not even getting into account, that it requires essentially zero
efforts from driver writers :)

-- 
	Evgeniy Polyakov
-
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

[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux