| ▲ | lukeschlather 4 hours ago |
| The frustrating thing about this is now you can't take screenshots of a Signal chat on Windows. Yes, you can use screenshotting to get around retention or whatever, but that's a basic feature. Another similar thing recently was I was trying to help a woman send a document to her lawyer, and for whatever reason I couldn't figure out how to share it with him via text or whatsapp. Somehow I was able to share it to my own phone via whatsapp, and from there I made a group text in Whatsapp with me and her lawyer to share the document. With AI agents I think we're similarly getting into territory where it's not so clear-cut as Signal is making things out to be. I share the knee-jerk "keep your agents out of my stuff!" reaction but I don't think that's a sustainable/pragmatic choice. It might be correct as a principle but if it locks you out of the operating system, it's not Signal's job to disable key OS features on the grounds that the OS is insecure - at a certain point Signal might as well just wipe the hard drive, but that's not Signal's role. Signal is there to enable people to send messages, not stop them from doing so. |
|
| ▲ | drnick1 4 hours ago | parent | next [-] |
| > The frustrating thing about this is now you can't take screenshots of a Signal chat on Windows. I find this surprising. What mechanism enforces this? This kind of restriction, AFAIK, is only possible on Android and iOS because users do not control the system (no "root" on user builds). On Linux, I certainly can screenshot Signal or any other "app" because the whole OS is under my control. |
| |
| ▲ | altairprime 4 hours ago | parent | next [-] | | Apps on the major platforms can opt specific windows into ‘do not allow screen capture or recording’: originally used for protected DVD content, it’s now also able to be used for secure credential entry dialogs or for Signal. The only defense against Linux will be tying device attestation status into Signal, so that I can see when someone I trust binds an untrustable client to our conversation. Linux is not necessarily an untrustworthy Signal platform, but as it stands today it is, as you point out, incapable of such protections and therefore ineligible for evaluating whether I can trust your client platform, and thus untrustable. (Unless you’re using a sealed Linux distro like Bazzite, in which case at least then one could reasonably determine whether your Signal instance is secured against local capture or not.) ps. Yes, trust is an onion, blah blah HDMI decoder boxes, etc, but I’m limiting the problem space to ‘software solutions only’, matching the problem space that the vast majority of AI device scanning of Signal content occurs in. | | |
| ▲ | drnick1 2 hours ago | parent | next [-] | | > The only defense against Linux will be tying device attestation status into Signal. I would stop using Signal if it required "attestation," which my GrapheneOS phone does not have anyway. | | |
| ▲ | altairprime 2 hours ago | parent [-] | | You’re implying ‘required’, but I’m not. Letting the other party in your conversation know whether your app and platform is secure against interception is not a requirement enforced. That’s between you and the other party. |
| |
| ▲ | lukeschlather 3 hours ago | parent | prev [-] | | The whole "don't trust the user's device" is almost even more problematic than it is for the DVD case. At least with the DVD case this is all by design getting in the user's way. This ends up being Signal stopping the user from doing something they want to do, on the grounds that Signal knows best (but the user is just forced to use a different app, eliminating the benefit.) | | |
| ▲ | altairprime 2 hours ago | parent [-] | | Doesn’t Signal already offer a checkbox that can be unchecked to allow the user to operate as they see fit on Windows? They said they’ll do the same on the other platforms in this post, so it’s unclear why users would be “forced to use a different app” rather than just unchecking a box. |
|
| |
| ▲ | tredre3 3 hours ago | parent | prev [-] | | It's also possible on Windows (SetWindowDisplayAffinity). What you call a restriction that takes control away from the user's control is actually an important security feature and Wayland will hopefully implement it (with user control I'm sure). It's not even hard to imagine why this is useful. Imagine you're sharing/streaming your screen and your password manager accidentally opens on the shared area. |
|
|
| ▲ | jddecker 2 hours ago | parent | prev | next [-] |
| There is an option in the Windows client in settings, under privacy, called screen security. If you turn that off, then you can take screenshots. |
|
| ▲ | skybrian 2 hours ago | parent | prev | next [-] |
| It's a bit awkward, but one workaround is to take a picture of the screen instead. |
|
| ▲ | XorNot 2 hours ago | parent | prev [-] |
| The problem with all things Signal related is that it eventually encourages people to think about things they're accustomed to not thinking about and so you get a lot of very silly outputs. With the biggest one being the number of people who apparently assumed that when they send a message to someone, that person couldn't just tell anyone else what they said anyway. |