cracked-behem
Re:Skiff – Privacy-first end-to-end encrypted email
on Wednesday August 23, 2023 @09:00AM (#37235173)
I built something that solves this problem. It uses an open source program installed on the client to encrypt and store data in a way that doesn't allow the website to access the plaintext data. https://redact.ws
Re:The coming war on end-to-end encryption
on Monday April 24, 2023 @05:50PM (#35693772)
Exactly. This section on the website should explain it with some more detail: https://redact.ws/how-it-works#client
Re:The coming war on end-to-end encryption
on Friday April 21, 2023 @04:48PM (#35659874)
The redact server is an open source application that runs locally on the client.
Re:The coming war on end-to-end encryption
on Friday April 21, 2023 @01:51PM (#35657503)
Not actively. It's open source so feel free to poke around our code and docs, and you can find a contact form on the site as well if you want to chat.
Re:The coming war on end-to-end encryption
on Friday April 21, 2023 @01:21PM (#35657060)
Nice! I worked on something that seems similar to this (https://redact.ws). Unfortunately there are a lot of challenges with adoption that seem difficult to overcome. One of the big challenges is that most people do not understand the nuances of privacy and encryption, and they aren't willing to jump through hoops to protect their data.
Re:Show HN: Working on a Zero-Knowledge Daily Journaling App
on Tuesday January 31, 2023 @11:52AM (#34597597)
Aren't the engineers controlling the backend also controlling the frontend? What's stopping the frontend from exfiltrating the encryption keys?