News for hackers. Stuff that matters.
Re:AES-GCM-SIV: Specification and Analysis [pdf] by p1mrx on Saturday March 04, 2017 @02:13PM (#13792382)
Do I understand correctly that the change from GHASH to POLYVAL is basically saying "screw tradition, let's put Little Endian on the wire"?

In general, when you see Little Endian on the wire, that means someone forgot to call htonl() in their code.

Re:AES-GCM-SIV: Specification and Analysis [pdf] by nbadg on Saturday March 04, 2017 @04:59PM (#13793130)
I'm reading that the same, but in this case it's a performance consideration; most systems expected to use AES-GCM-SIV use little-endian order internally, and since AES is often implemented at extremely low level (including in hardware), for most real-world systems (in particular, ones where crypto is extremely performance-sensitive), it doesn't make sense to impose an extra byte reordering for a value that is only used by the encryption process itself.