All the ciphers comply, so the bug is only a theroretical issue (but I
didn't check assembler versions --- they should be checked by the person
who wrote them, assembler is write-only language).
Since every current algorithm sets the flag could you invert
its sense? Sorry to have to do this to you :)
Thanks,
There may be external modules.
If you don't set the flag when it should be set, nothing happens (just a
slight performance drop), if you set the flag when it shouldn't be set,
you get data corruption. So the safest way is this meaning of flag, so
that not-yet-reviewed algorithms set the flag to 0 and prevent data
corruption.
Mikulas
--
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
