Protect application (and data) via password

Issue generated from Tuleap's migration script. Originally submitted by: Andreas Jahnke (ladon83)

Currently when the application (Ring-gnome) starts, you are automatically logged in.
This seems to be a security risk as anybody with access to the computer has also access to private messages.
Only workaround:
Unlink the account before closing.
However this is not usable in the real world.

It would be great to block the access via a password.
Whenever starting the application, a password should be needed (this can be optional of course).

EDIT:

This issue include:

• Encrypting histories on the device
• Encrypting the config

And that's not sufficient as the database is still accessible too.

Protecting with a password is obvious dangerous, since the sever never seems to recognize it. Tried on 3 new accounts and even 123 is not accepted. So can not add new device, can not restorer backup

I think an having an option to set a password/pin when opening the app is needed for security. The app can still run in the background and receive messages but requires a password/pin to open the app.

+1

changed title from Protect application via password to Protect application (and data) via password

mentioned in issue #763 (closed)

changed the description

mentioned in issue #779 (closed)

Also the conversation database should be encrypted weather a password is set on the account or not to prevent malware and other applications to read your conversations. Signal Messenger does it to ensure your conversations are safe.

mentioned in issue #979 (closed)

A masterpassword to unlock the userinterface and/or included accounts is a common feature (see FileZilla, Thunderbird, ... - and even in Skype you have the option to log out and require username + password to login again) and really necessary if you want a really secure communication application. So, if Jami wants to claim that for itself, I think the developers should implement such a feature. And "Use Skype instead of Jami if you want login security" seems a bit strange ...

Not likely to change but added to the feature request page

closed

added typefeature request label