Signal-desktop: [Feature Request] Add option to force re-authentication every time the desktop client is started

Created on 23 Nov 2016  路  4Comments  路  Source: signalapp/Signal-Desktop

  • [ x] I have searched open and closed issues for duplicates

Bug description

It would be awesome to have a setting that requires the QR code authentication each time the app is launched. This would be helpful for the usage of semi-private computers, or just general fear of computer confiscation.

Actual result: Desktop client authenticates once by scanning QR code on phone, then requires no additional authentication on subsequent launches.
Expected result: Setting to require authentication every time the desktop client is launched.

Platform info


Operating System: Windows/Linux
Browser: Chrome, Chromium

Signal version: 0.26.0

Feature Request

Most helpful comment

I think this is a very good feature to have on the desktop apps. I think it should function (as a user interface level) similar to the passphrase option in the android app. User can set a passphrase and an inactivity timer. The app is locked with the passphrase on initial startup or after inactivity, and cannot be opened or accessed without the passphrase. I don't know in what state of encryption the chats are stored on the desktop app -- encrypted would be good of course, but the could be implemented separately to the user interface passphrase, if that helps break up the task more.

Perhaps it may be wise to include an option on the 'locked screen' of the app the ability to reset the desktop client too.

All 4 comments

As a workaround you could de-authorize the client from within the app, though even that will only stop others from communicating on your behalf.

I agree with you strongly, that an automatic behaviour is ultimately more desirable.

the QR code will not help you with confiscation, as Signal-Desktop does not encrypt the saved messages.

You may however encrypt on file-system layer to archieve what you want.

Encryption at rest for the application data which requires a passphrase on start would likely meet your needs with greater security.

I think this is a very good feature to have on the desktop apps. I think it should function (as a user interface level) similar to the passphrase option in the android app. User can set a passphrase and an inactivity timer. The app is locked with the passphrase on initial startup or after inactivity, and cannot be opened or accessed without the passphrase. I don't know in what state of encryption the chats are stored on the desktop app -- encrypted would be good of course, but the could be implemented separately to the user interface passphrase, if that helps break up the task more.

Perhaps it may be wise to include an option on the 'locked screen' of the app the ability to reset the desktop client too.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

github-cygwin picture github-cygwin  路  3Comments

gesus14 picture gesus14  路  3Comments

bcsga picture bcsga  路  3Comments

PanderMusubi picture PanderMusubi  路  3Comments

ProactiveServices picture ProactiveServices  路  3Comments