Hi: I just noticed that the sha1 implementation in crypto4xx is fundamentally broken. It stores the hash state in the context of the tfm, instead of the context of the request. This means that at any one time you can only have one entity using the tfm, which is infeasible for an asynchronous hash. So I'm going to disable the sha1 part of crypto4xx until this is fixed. This hasn't caused a problem before because we haven't started using ahash yet, apart from tcrypt which is single-threaded. I'm currently in the process of converting authenc (hence IPsec) across, which means that we will soon rely on the fact that you can have multiple hash operations ongoing at once. Thanks, -- 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
