Email or username:

Password:

Forgot your password?
Meredith's posts Post Back to profile
Top-level
AlexTECPlayz

@metacolon "The reported issues rely on an attacker already having *full access to your device* — either physically, through a malware compromise, or via a malicious application running on the same device. This is not something that Signal, or any other app, can fully protect against. Nor do we ever claim to."

But Signal can take steps against this happening, by literally encrypting the attachments, this is possible, and we know it is, because many other programs have done it already. It's a basic feature Signal refuse(d)s to implement.

"The posters who raised this issue did so without contacting us directly. Instead, they went straight to social media, in some cases using inflammatory language. And they dropped these claims over a US holiday weekend. This is the opposite of responsible disclosure."

This is in bad faith. The issue was KNOWN for years, it was only brought back to light. Mysk doesn't need to contact Signal to talk about this issue, it's not something new.

13 July at 22:45 | Wall-to-wall | Open on techhub.social
3 comments
AlexTECPlayz

@metacolon Here are the GitHub issues. It goes as far back as December 2015.

github.com/signalapp/Signal-De

github.com/signalapp/Signal-De

And yet Signal closes both issues as 'Won't Fix', because apparently, people who don't have disk encryption (due to a multitude of possible reasons) can get fucked. The point of a security and privacy-focused project is to try and reclaim/secure as much as possible. What if someone is using Signal Desktop on a work computer, that CANNOT have disk encryption, for some reason? What if someone is using Signal Desktop on a public cafe computer, that doesn't have disk encryption?

Signal must account for all possibilities, and offer the option to enable data encryption at rest. I'm not trying to shit on Signal, but I'm not blind to suck them off and call everyone that criticizes Signal 'ungrateful'. I'm not specifically calling you out, just users in general, because I see a lot of people evangelizing Signal, on the same level as they evangelize Linux or Torvalds.

@metacolon Here are the GitHub issues. It goes as far back as December 2015.

github.com/signalapp/Signal-De

github.com/signalapp/Signal-De

And yet Signal closes both issues as 'Won't Fix', because apparently, people who don't have disk encryption (due to a multitude of possible reasons) can get fucked. The point of a security and privacy-focused project is to try and reclaim/secure as much as possible. What if someone is using...

13 July at 22:55 | Open on techhub.social
Meta

@alextecplayz
The issues you linked are about Signal storing stuff unencrypted. The only real new issue that came up with mysk imo is that you can clone a session. That's not in the issues and should have been a responsible disclosure.

Providing the option for a custom encryption password is something Signal *should* do. It's the same for mobile, which is why I'm using Molly. But it's not something they *must* do, as you imply. It's a valid feature request, not a bug.

The only thing Meredith said is impossible is to protect against full system access. I agree that it's a bit mialeading, but it is reasonable to assume that if someone can read your files, they can also read your screen. And Signal can't protect against that.

@alextecplayz
The issues you linked are about Signal storing stuff unencrypted. The only real new issue that came up with mysk imo is that you can clone a session. That's not in the issues and should have been a responsible disclosure.

Providing the option for a custom encryption password is something Signal *should* do. It's the same for mobile, which is why I'm using Molly. But it's not something they *must* do, as you imply. It's a valid feature request, not a bug.

13 July at 23:12 | Open on climatejustice.social
AlexTECPlayz

@metacolon Okay, the cloning session thing might be new, I haven't looked up on that. But I'm mostly talking about the attachment encryption issue here.

Yes, it's not something that Signal must do, but they should, considering they're always up talking about how privacy and security are so important. It's not a good look for a project dedicated to this, to ignore such a feature.

Apparently they did the data encryption at-rest for Signal on Android (before it was removed? and added back? by Molly) because Android didn't have "usable" FDE at the time.

And, come on, if WhatsApp has data encryption at-rest, I think it would be almost necessary for Signal to have it too, just because WA would be superior in this specific regard otherwise.

" but it is reasonable to assume that if someone can read your files, they can also read your screen" - this would depend on the OS. Linux has Wayland to prevent this, Android allows apps to prevent screen captures (screenshots would be blacked out).

@metacolon Okay, the cloning session thing might be new, I haven't looked up on that. But I'm mostly talking about the attachment encryption issue here.

Yes, it's not something that Signal must do, but they should, considering they're always up talking about how privacy and security are so important. It's not a good look for a project dedicated to this, to ignore such a feature.

13 July at 23:18 | Open on techhub.social
Go Up