-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Lock App + Encrypted Database #1850
Comments
As previously discussed, you can use the guest account available in your OS of choice for that 'friend using my computer' scenario. Maybe you can talk a little about why you feel things have changed with the Standalone app? |
not necessarily, ie they need to work with your apps/data, so it makes sense to lock-protect the app. Also the data should be imho stored only in an encrypted way, as even with FDE, once the computer is on, all the data is unlocked. A virus can access your conversations on disk. if the data is kept encrypted (in RAM also?) and on disk and only decrypted by the app when needed, this can be reduced. A final touch would be if Signal could store its keys in TPM for extra security? |
As a quick gut check, a few more questions:
|
Yes, I log off easily, as all "important" sites are logged in in the "porn view", so it's just a matter of killing a browser window.
Could not, webmail. But I see your point, in many reasonable cases they could impose me (ie skype, etc). I feel the thing is:
I was looking into the "Implementation POV":
|
I totally agree with @breznak about at least a configurable password protection. I can spend some time on developing this feature if you think it's nice to have. In fact, I think having two passwords would be great to have:
Who talked about being privacy-freak? :) |
Decoy behavior is not something we've put in place on any of the Signal apps, so I don't think we want to do that yet. Regarding the password, you're welcome to start brainstorming visual designs and potential code changes, but we're not ready for a pull request yet. |
I'm not in a hurry either :) I have lots of things on my desk, but still, I would like to contribute as much as I can. |
fwiw, I really like the idea of a Lock function/button for the desktop app, too. Something like the way it is on the Android app would be great. I'd make it myself if I knew how. |
On Mac consider encrypting locally stored data with key stored in Apple's Secure Enclave, available on most recent Mac platforms: https://developer.apple.com/documentation/security/certificate_key_and_trust_services/keys/storing_keys_in_the_secure_enclave |
In addition to what is mentioned by @resu, I also suggest encrypting the encryption key with the app password which is sitting in Paging @scottnonnenberg , @canerelci |
I'm new to the desktop app (macOS) and I'm surprised there's no way for me to lock the app, whether manually or automatically. Setting timeouts and reauthentication for local users is basic op-sec |
+1 for me. I find weird I can lock my app on mobile but not on my computer. It makes no sense! |
Ikr. This is a much needed feature as Signal is often referred to as the golden standard of private messaging. If its desktop client is vulnerable, it kinda defies all the benefits of having a robust mobile app imo. |
Doesn't the android client have a similar vulnerability? It has encrypted storage, but how is the key stored? First of all, signal-desktop needs to have encrypted local storage. Critically, the user should be able to configure signal to require a user-entered password to decrypt the local storage upon startup. This may require changes in both desktop and mobile. This vulnerability means someone can login as you and spy on your future conversations from another device. It would be great if signal servers could help combat this by:
|
There's also a very practical use case where you're using Signal on a PC that's not your own, e.g. a company-owned device where your account is controlled by the company via active directory or the like, and they have the ability to change your password and log into the device as you once you leave the org. Having a pin or password on the app is a simple way to ensure your Signal conversations remain secure despite the fact that you don't have ultimate control over the environment you're operating in. |
Absolutely would love to see this feature implemented. I understand all the conversations against it, but above post explains it in full, not sure why devs do not want to provide such an option: just an additional layer of security. Telegram has something like this implemented; such as every few second the app window gets blocked; requiring pin to unlock. |
I was shocked to see that Signal Desktop is unencrypted, I could extract everything. If somebody knows of a fork that implemented something like this, would be great. Hope that Threema when they implement Multi-Device Support will do it right and hope that Signal goes the right way. I think Signal is a great great product, but what I hear and read and get is like that unsecure ways are defended. |
I was rather astounded to learn that this application stores ALL signal conversations in plaintext. Even if you have sensitive, secure conversations on Signal, linking to the desktop app to the mobile app immediately defeats all protection on every conversation. While I get the idea of FDE, implementing even the most basic of encryption for messages is absolutely essential in my humble opinion. |
True. Its the same reason a password Manager is locked and only unlocked in RAM, so no App or so can extract all passwords. Private messages could be similar of value for protection then your passwords. I know that malware can get any data, once on PC, but it can still be mitigated for malware that just copies files from disk. Else locking a password manager would be as same useless and it is done on every one you can find (even the less secure way and saving them in a browser can be protected via a master password or via windows hello). Jus thought maybe to make a script that encrypts the key and pictures when closed, better than nothing, but problem: unencrypted data on disk while opened. Unencrypted data should only be in RAM. |
What i'm surprised is that people learned about this issue so late. This has been publicly reported from Oct 2018 and here from 2015(#452). |
Well it's time to fix it. I've seen it here too. I was also shocked. Someone wrote here that the conversations would be stored in plaintext, that's not really true. What is true is, that the enc key is unencrypted in the dir (more exactly the json in the dir) which makes it very easy for a common attacker to extract the data out of the sqlite db. But I'm not sure if the guy above knows that a fingerprint is very "secure" (just a hint it's not). |
Thats great, thanks @ksaadDE a password encryption would be the first step. Enabling Windows Hello to unlock it would be a next step (for Windows users) and can be discussed after any encryption with a password is available. |
Yes, of course. Step by step.
I just ask you: Do you think anyone provides Signal or any other privacy or security-oriented App to OS like Windows or iOS/OSX just because they are secure or just due to the convenience and maybe the leading to a handover to more secure (and privacy-oriented) Systems like Linux or FreeBSD? If you are serious about honesty, your personal security and privacy, don't use Windows or iOS/OSX (and so on). Don't waste your time with Windows Hello. Even it is secure for a while, Microsoft will always rate their company growth and financial income higher than their protective intentions. They just don't care about the Users privacy and even not their security, although they're telling it in the advertisements - which can just be interpreted as a bad joke xD Another topic is that they don't think about what they do. Just imagine: larger criminal organisations, not telling anyone, already abusing the flawy implementations and backdoors build-in for the "good". What is the good, if the outcome is horrible? Also, a side note: I don't blame the Devs at Apple and Microsoft for it (just two examples, randomly picked). They're just doing their job. Some of them are highly accepted members of the Open Source Software Community, and most of us like them in the sense of their expertise. Even the APT Defenders at Microsoft and also Apple are just good people working at the more or less "wrong" side. Also, a note to TPMs. If they rely upon closed source Hardware or closed source Software (unlike intel does, since they have a TPM-oss stack here on Github), they can't be secure! Another question I asked myself.. does a computer in a computer making my computer securer? I think we will look forward to implementing stuff for TPMs, if the attestation stuff, crypto-capabilities, and so on, having common and stable libraries (for Electron and Chromium), which is not yet the case. |
@ksaadDE Signal is available on Windows, MacOS, Google Play Store, App Store (iOS), as long as it is there it should use secure features from theses OSs. Think like Signal would not include fingerprint login on Android, because we can't trust Samsung, or any other manufacturer and not Google. Signal will only be good, if many people are using it and that way people have to be gathered where there are at and people at companies maybe don't have a choice of their OS. |
Thanks for agreeing. Well, we are only able to convince people, that's the whole point of freedom in Software and Hardware. It's not about supporting these garbage OS, it's just showing them how better Software and Hardware works. That's why we shouldn't rely on their horrible flawy implementations, instead, let's make them (only if needed) the last option. Yup, we can't trust Intel and other closed Source manufacturers, but the good thing is: they try to provide us with Open Source in their new products. They see the issue and shifting towards us. More in Software than in Hardware, but it will also shift towards Open Source Hardware soon. Until the new age arrives we have to bridge between Open Source Software and Hardware (and closed Source Hardware). If I remember correctly these CPU Backdoors were very soon fixed on the Software side, especially in the Linux Community. Greetz |
should be fine now see PR #5465 |
Since recently migrating from a chrome add-on, I feel we should revisit adding an optional lock screen & optional database encryption for the standalone application.
While FDE is totally an option, and something I already use, I would like to be able to lock the standalone application if I wanted to let a friend jump on my system to browse amazon or play a game, without worrying they might get curious and click on the application only to stumble on my private conversations without any type of wall.
Referencing #452, #550, #710, #790, #972, #1017
The text was updated successfully, but these errors were encountered: