Existing security/crypto APIs in JDK are all BYTE constrained. So, the implementation will be "BYTE-only". Are you suggesting to explicitly mention in the SHA-3 JEP that these algorithm impl will be "BYTE-only"?
Valerie
On 4/21/2016 1:40 AM, e...@zusammenkunft.net wrote:
Hello, Just noticed, the validation program allows BIT- or BYTE-only APIs, the existing ones are all BYTE constrained. That would be a good definition in the JEP: http://csrc.nist.gov/groups/STM/cavp/documents/sha3/sha3val.html Gruss Bernd
