Lacross browser is a process that runs on top of chromeOS. The lacros browser has an entirely different version number from the OS and is updated independently from the OS. It is not as integrated into chromeOS as the original chromeOS browser. But then I logged out and logged in with master password, and repeated the experiment with same results (hence, probably not relevant)Īdditional info about lacros browser on chromebook (which is what I am using) Probably not relevant: I first noticed this behavior after login with device. Can anyone shed any light? Does it act the same in browsers of other desktop operating systems (not chromeOS)?īitwarden chrome extension version 2024.1.1Ĭhrome browser version: Version 1.85 (Official Build) lacros (64-bit)ĬhromeOS version: Version 1.235 (Official Build) (64-bit) Viewed my vault contents (without having ever re-entered my master password!) Unlocked my chromebook (entered chromebook pin)Ĭlick on extension icon, prompted for bitwarden pin. Locked my chromebook (requires chromebook pin to get back in) Verified my vault was locked (shows locked icon and asks for pin when I click, which I did not provide).Ĭlosed all other applications on my chromebook (no applications highlighted as running on the shelf) Tap profile picture and then tapped "lock now" Settings / unlock with pin (kept "require master password on browser restart" checked) Initial condition: logged into the bitwarden chrome extension in lacros chrome browser of my chromebook When I pin-lock the bitwarden extension and keep the option checked "lock with master password on browser restart", it does NOT seem to require master password on browser restart (it lets me back in with pin).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |