This is great -- sorely needed and long overdue. Thanks for sharing the code and good luck with the company!
Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
31–40 of 80 posts
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#32Earlier quoted context omitted.
Yeah, this is definitely a risk of any in-browser demo of this tech. The story for apps is much better, since there's a routine installation process, signatures are checked, etc. We'd like private retrievals to eventually be part of the browser itself, so that it can make a kind of "private GET" request natively. We'd also love to bind our client JS code to a hash of our build output from GitHub, but as of now there'…
I wonder how the Subresource Integrity can expand to the root document hash (other than using IPFS gateways). UPD yeah, extension hashing resources sounds nice too
I've wanted this too! You could include subresource integrity hash in the URL that the browser will check against the page. This would make things like Cryptpad and Skiff, or group invite links in Signal, way more secure.
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#33[dead]
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#34Congrats on the launch! I actually considered launching something tangential - though I never figured out who the customers would really be nor how I would pitch this to companies. Excited to see where this takes you!
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#35Exciting times.
OpenAI's GPT-4 announcement, Google announcing AI for Workspace, Meta additional 10k layoffs, and now we're seeing homomorphic encryption come out to the masses.
All in one day!
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#36I read homophobic encryption as a service and was seriously confused
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#37Might just be my browser, but on the homepage, both the "scan for breached credentials" and "block malicious URLs" links both lead to the password checker when clicked.
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#38this is great, thanks for launching it, I may actually be a future user of yours ;)
one important feature I see missing is that one cannot run queries with comparisons, such as "give me any message sent between 2022-10-10 and 2023-02-01". This would be very important when one doesn't have all the keys, or when the keys are too many, like in the messages example above.
Any idea for this kind of scenario?
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#39Congrats on the launch! I actually considered launching something tangential - though I never figured out who the customers would really be nor how I would pitch this to companies. Excited to see where this takes you!
Thanks! Yup, private retrieval is interesting as a product because it's a fundamentally new capability; there aren't really competitors we can show incremental improvements against. If you're still interested in the space, we'd be happy to compare notes! Feel free to email us: founders AT blyss.dev
Re: Launch HN: Blyss (YC W23) – Homomorphic encryption as a service
#40I'm guessing this solves a very specific pet peeve of mine:
When your bitwarden vault is not opened, if you log in to website, the extension will ask if you want to store the password, even if your vault already has an entry for that website. Of course, this is by design so that bitwarden doesn't store websites you have credentials for in plaintext (unlike lastpass and it blew up in their face).
Would this allow your browser to query a database of "domains i have a password for" without a leak on bitwarden's server exposing this exact database? There are other implementation details but you get the idea.