281–290 of 305 posts
Earlier quoted context omitted.
Former Googler here. E2EE is easy. Nobody gets promoted at Google for solving easy problems. In fact if you set out to solve an easy problem, it looks bad at performance review time.
How is E2EE easy?
Earlier quoted context omitted.
I should have bracketed out GCP as a theoretical application for this. I was referring to the Google consumer extended universe.
Which is also learning how to monetize their offering via cloud instead of ads. So again your expertise here is questionable.
Earlier quoted context omitted.
You literally don’t know who I am or the roles I had. So unless you can tell me how many steps you were from Kent Walker and what you worked on I’m gonna bet a hell of a lot I know more than you. Edit to clarify my prior point: some of the technology makes it into the product, but the putative data protections do not. Why? Because there is always a work around, and ads legal will approve it every time.
and you don't know who I am. I might have been closer to that work than you would know.
Thats the embarrassing part, you know “don’t be evil” went out the window years ago, yet still think you’re making a difference with your little bit shifting games. As if the moment the work you do bumped against against revenue it would hold.
Earlier quoted context omitted.
There are many challenges we need to solve for privacy preserving compute. Legislations, legal matters, key management, HSM like devices that has limited compute capabilities. At Belfort, we are accelerating FHE, besides exploring such uses cases for FHE. Like this one with Google, we also have publishes use cases; https://belfortlabs.com/blog/encrypted-fraud-detection-with-... https://belfortlabs.com/blog/belfort-pa…
The advertising case seems to be solved by local models as well, then the data doesn't even need to be sent to the server. The Swift one is interesting, but I don't understand why the transaction needs to be encrypted, or more specifically why the model can only run in the encrypted part of the pipeline. Super cool tech, but I guess I just don't see the application yet. And wow, I worked with Marc a decade ago, small…
Suggesting alternative approaches to such large corporations is not straightforward. Their IT and security teams cannot afford to risk handling sensitive financial data in plaintext. No manager would readily approve a solution that offers additional functionality at the cost of deviating, even slightly, from well-established compliance practices. Encryption is therefore fundamental to how these systems operate.
The challenge arises when these institutions need to perform computations or checks on such encrypted data. Decrypting the data, even under controlled conditions and with trained personnel, is operationally complex, introduces additional risk, and can create a significant compliance burden.
This is where FHE offers a compelling solution. We demonstrate how a check can be performed directly on encrypted transactions against a known blacklist, without requiring the underlying transaction data to be decrypted.
P.S. It is great to work with Marc :)
Earlier quoted context omitted.
At that kind of amount of waste putting 2U server with some GPUs in hospital would be cheaper
Making things 10x more expensive to reduce legal liability is what hospitals are all about
I see a lot of comments here about how private AI is much cheaper than doing this, and that is currently true. But I am curious if anyone can think of any use cases for this as it currently stands? For every idea I can think of, I can think of another solution that would probably be a better solution at current slowdown in cost from using homomorphic encryption. For their two examples... 1) For the "will they click t…
If the bottleneck is data transfer rate or volume, then I think you’ll find more use from today’s FHE. Incidentally there is a fair amount of overlap in the use case space between homomorphisms and oblivious transfer.
So, by that logic, we are potentially looking for a problem space where their is a large amount of data that is too large to even be paged through by the client, and where the FHE would actually make financial sense relative to downloading it?
I'll think about that, but nothing immediately comes to mind.
This is the same Google that doesn't have e2ee on their password manager by default. Like WTF, it's a password manager.
Earlier quoted context omitted.
Which seems massively worse than a real local device in fact 2x is probably untenable to the point of uselessness because actually privacy sensitive matters need actual privacy that can't be defeated by your government telling Google to serve you compromised js and spy on you anyway and most people don't give 2 shits about privacy so they won't pay 10% more let alone 2x. I'm glad people fund things that are only of i…
I think you have completely wrong use cases in mind. You will not use this for normal compute workloads. Typical use cases are for doing biometric authentication without giving your biometric information, or sensitive queries using medical information. Apple has homomorphic encryption in image search. You can use your own photos encrypted into the cloud to search for landmarks in the image without revealing photos. P…
Earlier quoted context omitted.
LastPass, designed for regular users and one of the most popular password managers, had a breach of user vaults. If they hadn't implemented E2EE then it would have been more devastating than it was (crypto wallets were found from vaults with weak master passwords).
Google's security record at avoiding that kind of breach is just about the best in the industry, and their system that handles custody of password manager secrets is designed to withstand even a compromise of their production infrastructure ( https://security.googleblog.com/2022/10/SecurityofPasskeysin... ). I would advise almost all users to worry more about getting locked out of their password database than about t…
They can still and should still continue using great security practices while protecting E2EE data.
>Of course, I would also advise almost all users not to self-custody cryptocurrency.
There's no point in crypto if you're not holding your own keys. It's the antithesis of cryptocurrency. People can have highly secure self custody wallets on a modern iPhone or Pixel. And their seeds would have been safe if LastPass didn't have terrible security or they used long passphrases.
So much inefficiency just to run it on someone else's untrusted hardware. Private AI is already possible today with local open-weight models running on hardware you control. Homomorphic encryption is cool technology, but I'm really not sure what problem it solves.
I bet this would've been ground breaking if this was an announcement from Apple though.