The coming war on end-to-end encryption

Re:The coming war on end-to-end encryption by EGreg on Friday April 21, 2023 @04:45PM (#35659827)

I like the intent of this! My main question is, how do we know redact.ws won't suddenly serve different Javascript one day, to certain clients, which send unencrypted payloads somewhere?

[ Parent | on HN ]

Re:The coming war on end-to-end encryption by cracked-behem on Friday April 21, 2023 @04:48PM (#35659874)

The redact server is an open source application that runs locally on the client.

[ Parent | on HN ]

Re:The coming war on end-to-end encryption by EGreg on Friday April 21, 2023 @07:07PM (#35661457)

How does a server run on the client? It runs on localhost! Right?

It can show the user their own info back to them in iframes?

[ Parent | on HN ]

Re:The coming war on end-to-end encryption by pcthrowaway on Friday April 21, 2023 @08:00PM (#35661854)

I'm not the creator of redact, but it sounds like you're under the impression that the iframe src is redact.ws in which case I'd understand your concern.

My assumption is that the iframe src would be the local redact server, which would keep things as secure as the package the user installed (though there could be compromises at the network level I suppose)

[ Parent | on HN ]

Re:The coming war on end-to-end encryption by cracked-behem 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

[ Parent | on HN ]