News for hackers. Stuff that matters.
Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by bawolff on Tuesday February 14, 2023 @12:33AM (#34785800)
> That seems very wrong ((as far as I know) those standards are not in any way designed in such a way as to permit operations on their cyphertexts).

Those standards are meaningless by themselves without specifying a mode (e.g. GCM, CTR, CBC, ECB, etc). A thing people sometimes try to do with them (no idea if this is what vaulttree is doing) is use some less secure mode that is determistic and do equality matching (this is almost always a bad idea and usually leaks way more than you would naively assume). For example, if you use ECB mode you can search as long as you are searching along block boundries.

https://www.microsoft.com/en-us/research/wp-content/uploads/... is an interesting paper about this sort of thing.

Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by yarg on Tuesday February 14, 2023 @01:09AM (#34786039)
Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by l33t233372 on Tuesday February 14, 2023 @01:25AM (#34786126)
ECB should never be used under any circumstances. Library creators would do well to rename their functions along the lines of ECB_NEVER_USE_THIS_IS_NOT_SECURE.
Re:Google’s Fully Homomorphic Encryption Compiler – A Primer by bawolff on Tuesday February 14, 2023 @06:41AM (#34788033)
In case it wasn't clear from my comment - i agree 100%