I really don't like seeing security software use non-constant-time
baseFOO coders, even for ‘public’ keys.

See attached for an example of constant-time base16 encoding/decoding
(undocumented and barely tested, but I don't think there's any room
for it to have subtle bugs).


Robert Ransom

Attachment: 2014-02-05-01-ct-base16.tar
Description: Unix tar archive

_______________________________________________
Messaging mailing list
[email protected]
https://moderncrypto.org/mailman/listinfo/messaging

Reply via email to