4 ms·
At first I was a bit puzzled why anyone would need to describe an editor as "secure"... but oh well, it is actually a web application. I can see the need now.
by raimue 11y ago
At first I was a bit puzzled why anyone would need to describe an editor as "secure"... but oh well, it is actually a web application. I can see the need now.
- sitkack 11y agoI cannot vouch for the security the editor mentioned here, but anything that handles external data has security concerns. https://www.cvedetails.com/vulnerability-list/vendor_id-8218/opec-1/VIM.html https://www.cvedetails.com/vulnerability-list/vendor_id-8218... https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3075 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3075
- kybernetikos 11y agoDid you read the article? It's an interesting way of making a rich shareable document that is readable by those you share the link with and not by anyone else, including those who operate the server, or those on the network route to you. Well, that's the principle, I didn't look closely enough to see if their implementation can be trusted, but it's a fun idea.
- RadioactiveMan 11y agoSince the encryption key is in the URL I don't think it's fair for them to claim they can't decrypt.
- willdurand 11y agoIt is in the hash/fragment of the URL, that part is client side only and is never sent to the server.