Hidden profiles and 'reveal' code #637

New Issue

serrq · 2023-03-01T07:37:24Z

serrq commented

2023-03-01 07:37:24 +00:00

Probably many of us have more than one profile and it also seems convenient to be able to use the same password for ten profiles, so that you can recall them all at once as needed.

However this practice hides a problem:
There is no way to let the app know that a profile should not be revealed despite having the master password.

The reveal code acts as a 2FA, and if set in the target profile, it hides its visibility until you enter the second password which is the 'reveal' code.

That’s when it comes out.

Of course, to make sense, the reveal code can be switched on/off as your needs.

Probably many of us have more than one profile and it also seems convenient to be able to use the same password for ten profiles, so that you can recall them all at once as needed. However this practice hides a problem: There is no way to let the app know that a profile should not be revealed despite having the master password. The reveal code acts as a 2FA, and if set in the target profile, it hides its visibility until you enter the second password which is the 'reveal' code. That’s when it comes out. Of course, to make sense, the reveal code can be switched on/off as your needs.

sarah commented

2023-05-08 19:19:28 +00:00

The risks associated with hidden profiles are non-obvious.

Either:

The hidden profile is "active" in which case it can be trivially determined to be active via on-device inspection - this is hard to communicate to users.

Or

The hidden profile is inactive until the second-password is entered. In which cases this is functionally equivalent to encrypted the profile with a different password anyway.

After consideration, I'm closing this issue as wontfix. Please feel free to reopen if there is a stronger argument for this functionality.

The risks associated with hidden profiles are non-obvious. Either: 1. The hidden profile is "active" in which case it can be trivially determined to be active via on-device inspection - this is hard to communicate to users. Or 2. The hidden profile is inactive until the second-password is entered. In which cases this is functionally equivalent to encrypted the profile with a different password anyway. After consideration, I'm closing this issue as wontfix. Please feel free to reopen if there is a stronger argument for this functionality.

sarah closed this issue

2023-05-08 19:19:29 +00:00

Sign in to join this conversation.