• 1 Post
  • 18 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle


  • Yes but it pushes it to an operating system level and that means everyone wins as the operating system solutions to improve as vulnerabilities are found and resolved.

    You also don’t need rce access to exfiltrate data. If decrypted keys are held in memory, that mitigates an entire class of vulnerabilities from other applications causing your private chats from leaking.

    Full disk encryption is not a solution here. Any application that’s already running which can provide read only file system access to an attacker is not going to be affected by your full disk encryption.


  • They don’t necessarily need RCE access.

    Also this isn’t how security works. Please refer to the Swiss cheese model.

    Unless you can guarantee that every application ever installed on every computer will always be secure under every circumstances then you’re already breaking your security model.

    An application may expose a vulnerable web server which may allow read only file system access without exposing the user to any direct control of their computer from an attacker. Now your lack of security posture for your application (signal) now has a shared fate to any other application anyone else built.

    This is just one of many easy examples that are counter to your argument here.


  • Having Signal fill in gaps for what the OS should be protecting is just going to stretch Signal more than it already does. I would agree that if Signal can properly support that kind of protection on EVERY OS that its built for, go for it. But this should be an OS level protection that can be offered to Signal as an app, not the other way around.

    Damn reading literacy has gone downhill these days.

    Please reread my post.

    But this should be an OS level protection that can be offered to Signal as an app, not the other way around.

    1. OSs provide keyring features already
    2. The framework signal uses (electron) has a built in API for this EXACT NEED

    Cmon, you can do better than this, this is just embarrassing.


  • That’s not how this works.

    This sort of “dismissive security through ignorance” is how we get so many damn security breaches these days.

    I see this every day with software engineers, a group that you would think would be above the bar on security. Unfortunately a little bit of knowledge results in a mountain of confidence (see Dunning Kruger effect). They are just confident in bad choices instead.

    We don’t need to use encryption at rest because if the database is compromised we have bigger problems” really did a lot to protect the last few thousand companies from preventable data exfiltration that was in fact the largest problem they had.

    Turns out that having read access to the underlying storage for the database doesn’t necessarily mean that the database and all of your internal systems are more compromised. It just means that the decision makers were making poor decisions based on a lack of risk modeling knowledge.


    That said the real question I have for you here is:

    Are you confident in your omniscience in that you can enumerate all risks and attack factors that can result in data being exfiltrated from a device?

    If not, then why comment as if you are?



  • That’s not how this works.

    If the stored data from signal is encrypted and the keys are not protected than that is the security risk that can be mitigated using common tools that every operating system provides.

    You’re defending signal from a point of ignorance. This is a textbook risk just waiting for a series of latent failures to allow leaks or access to your “private” messages.

    There are many ways attackers can dump files without actually having privileged access to write to or read from memory. However, that’s a moot point as neither you nor I are capable of enumerating all potential attack vectors and risks. So instead of waiting for a known failure to happen because you are personally “confident” in your level of technological omnipotence, we should instead not be so blatantly arrogant and fill the hole waiting to be used.


    Also this is a common problem with framework provided solutions:

    https://www.electronjs.org/docs/latest/api/safe-storage

    This is such a common problem that it has been abstracted into apis for most major desktop frameworks. And every major operating system provides a key ring like service for this purpose.

    Because this is a common hole in your security model.