News for hackers. Stuff that matters.
Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by Dylan16807 on Monday February 13, 2023 @11:16PM (#34785219)
Since it encrypts one bit at a time, does capitalizing even have to touch the 224 bits that don't change?

> wouldn't add.cc take 64 wires?

Plus another hundred intermediate wires. And it's doing more complicated operations, however much that matters.

Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by squeaky-clean on Tuesday February 14, 2023 @02:11AM (#34786401)
No idea lol! Though it says it works on all 32 bytes in parallel regardless of input size. I imagine ignoring the bits that don't change would be some sort of security vulnerability? You could probably work out some timing attack or entropy reduction otherwise? They state it should take the same duration regardless of the length of the input string or how much needs to be capitalized (all branches are executed even though many are discarded)
Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by Dylan16807 on Tuesday February 14, 2023 @02:27AM (#34786491)
> I imagine ignoring the bits that don't change would be some sort of security vulnerability? You could probably work out some timing attack or entropy reduction otherwise?

Nah. The bits are hardcoded into the circuit to not change. That's part of the program, and the program is public information. Only bit 6 of each byte might change, and everyone knows it.

Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by squeaky-clean on Wednesday February 15, 2023 @09:44PM (#34814315)
Whoa, I never knew about the ascii 6th bit trick, I've never really considered capitalization wasn't some random offset. So that does make this circuit simpler than I thought it was, and there's the parallelism aspect. It's not so surprising now that it's faster than the add.