3 ms·
SendSafely's workflow is quite different[1] from what I described with the encrypted static HTML email attachment. And I don't like the idea of sharing the conf
by devy 9y ago
SendSafely's workflow is quite different[1] from what I described with the encrypted static HTML email attachment. And I don't like the idea of sharing the confidential data over 3rd part cloud storage even if it's encrypted.
[1]: https://www.sendsafely.com/howitworks/ https://www.sendsafely.com/howitworks/
- wyc 9y agoI agree there are differences, including transit route and format. Here are the similarities I saw: - Payload is encrypted client-side by the sender - Encrypted payload is decrypted client-side by the receiver - 3rd party provides the unlock passphrase I think I'd much prefer standard AES to AES sprinkled with a bit of proprietary magic, as the latter is more likely to introduce new attack vectors than not.