4 ms·
I could imagine Signal Desktop adding a mail-like UI that still interops with Signal.
by wmf 7y ago
I could imagine Signal Desktop adding a mail-like UI that still interops with Signal.
- tptacek 7y agoSomething like that will eventually happen, because lots of people want a good desktop mail-like experience for secure messaging. And there's nothing wrong with that, as long as the backplane for such a system isn't SMTP email. It's not the core email UX that's the problem; it's SMTP email that's the problem.
- caf 7y agoWould such a desktop client have to disable copy-to-the-clipboard, because otherwise you won't be able to stop bozos from copy-and-pasting from this new system into an MS Outlook all-company email?
- tptacek 7y agoNo. The problem this article is talking about isn't "bozos".
- caf 7y agoWhat I mean is, doesn't the ubiquitous presence of ordinary email on the desktop create an unacceptable risk of the "inevitable unencrypted reply" for any secure messenger on the desktop?
- lvh 7y agoTop practitioners like Zimmerman himself famously replied unencryptedly to encrypted messages. Copy pasting something in a different program seems hard to do by accident. But sure, let’s stipulate we break copy paste :)
- jackpirate 7y agoIt's not the core email UX that's the problem; it's SMTP email that's the problem. You're article seems to argue the opposite to me. For example, the following quotes are all related to the email UX: 1. In any group of people exchanging encrypted emails, someone will eventually manage to reply in plaintext, usually with a quoted copy of the entire chain of email attached. 2. Every archived message will eventually leak. My understanding is that it would be possible to create an alternative app that is compatible with the Signal protocol that would provide a different UX. This alternative UX could, for example, offer the ability to save all messages onto google docs, eliminating the benefits of secure messaging.
- tptacek 7y agoThere is nothing about the core UX of email that requires plaintext as an option; you can straightforwardly imagine, and probably even readily implement, a secure messenger with the same UX as Outlook in which it's not possible to plaintext-reply a message, or send plaintext at all. Archival is a problem. But you can also imagine something with the UX of Outlook that implements the same advisory-level disappearing messenger feature that modern secure messengers have; in fact, I wouldn't be surprised if you told me Outlook already has that feature (but that it only works for Outlook users). The problem is the legacy of SMTP. It's not what the UI looks like.
- TylerE 7y agoPretty hard to block PrintScreen though.
- schoen 7y agoThat feature isn't trying to prevent people from deliberately archiving or forwarding messages in a way that the sender didn't intend, expect, or prefer.
- lvh 7y agoSure! But a screenshot is trivial to forge anyway, and even if you block PrScrn, people can always taddle. The goal is to get the message safely to the recipient, not prevent the recipient from disclosing anything afterwards. (Non-repudiation is a common goal, but screenshots being easy to forge solves that.)
- deleted 7y ago[deleted]