As for SHA256/512, the SHAKE (and SHA3 in general) go implementation continues to be not fully in line with the RFCs/specification, because there is no way to have a HASH/SUM/MAC of inputs that are not aligned to the byte. Say, for example, 12 bits. Of course, padding before hashing cannot be the solution. For how the implementation is done, the only possibility to override this limitation is to work into the shake.go (example) file, which has a lot of drawbacks. I think that if correcting is impossible, at least the limitation should be clear in the documentation.
Thanks, Paolo -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/118ff882-a3b4-4884-9876-d69ad13bf6ccn%40googlegroups.com.
