$ ./expn64v2gcm -len 8192 -iter 1000000 AES-128-GCM: Key schedule: expanded (64-bit path) Total data: 8.19 GB Time: 2.34 s Throughput: 3500 MB/s Cycles/byte: 1.28 (on 3.2 GHz CPU)
You might ask: Why not just call it "EncryptData"?
The code is stable enough for non-production experiments. The real value isn’t today—it’s six months from now, when every major cloud provider quietly enables expn64v2gcm by default for internal control-plane traffic.
What it actually means: Traditional GCM uses a fixed 12-byte nonce. If you reuse a nonce with the same key, catastrophe strikes (the famous “forbidden attack”). expn64v2gcm appears to add a —turning short nonces into 64-byte internal states before GCM even runs.
$ ./expn64v2gcm -len 8192 -iter 1000000 AES-128-GCM: Key schedule: expanded (64-bit path) Total data: 8.19 GB Time: 2.34 s Throughput: 3500 MB/s Cycles/byte: 1.28 (on 3.2 GHz CPU)
You might ask: Why not just call it "EncryptData"?
The code is stable enough for non-production experiments. The real value isn’t today—it’s six months from now, when every major cloud provider quietly enables expn64v2gcm by default for internal control-plane traffic.
What it actually means: Traditional GCM uses a fixed 12-byte nonce. If you reuse a nonce with the same key, catastrophe strikes (the famous “forbidden attack”). expn64v2gcm appears to add a —turning short nonces into 64-byte internal states before GCM even runs.
