Messages in this thread | | | Date | Mon, 11 Aug 2003 00:46:01 +1000 (EST) | From | James Morris <> | Subject | Re: [RFC][PATCH] Make cryptoapi non-optional? |
| |
On Sat, 9 Aug 2003, David S. Miller wrote:
> > Also, I posted to cryptoapi-devel that I need a way to disable the > > unconditional padding on the hash functions. > > James, comments?
Yes, a flag could be added for crypto_alloc_tfm() which disables padding for digests (e.g. CRYPTO_TFM_DIGEST_NOPAD).
Given that there are a still a number of unresolved issues, e.g. making the crypto api (or a subset thereof) mandatory, perhaps it would be more appropriate to slate these changes for 2.7 and then backport to 2.6 once stable.
- James -- James Morris <jmorris@intercode.com.au>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |