> Ah, now I see it. Yes, all AES 128 are covered. > > What about AES 192 and 256? The implementation doesn't support them, and I didn't add them. It would require either: * Trickery based on the supplied seed length, which would conflict with the existing optional-DT support, or * A separate crypto_alg for the different key (and therefore seed) sizes. -- 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
