Am Donnerstag, 15. September 2016, 13:58:08 CEST schrieb Herbert Xu: Hi Herbert,
> Where's the pain point here? For cases like seqiv where you want to > say if X is FIPS-allowed then so is seqiv(X) we can certainly add > some code to testmgr to cater for that instead of listing them > individually. Where shall we draw the line here? Shall that be only for authenc, or seqiv? Or shall we also consider rfc4106 too, knowing that there are implementations which provide a full rfc4106 GCM combo (x86 for example). What about the current pkcspad1 template where we could expect that there may be entire HW implementations with that? Ciao Stephan -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
