![RTFM! DevOps[at]UA](https://substackcdn.com/image/fetch/$s_!ruIs!,w_80,h_80,c_fill,f_webp,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F78e47926-bd0f-4929-a081-2588cc2a3d82_90x95.jpeg)
![RTFM! DevOps[at]UA](https://substackcdn.com/image/fetch/$s_!ruIs!,w_36,h_36,c_fill,f_webp,q_auto:good,fl_progressive:steep,g_auto/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F78e47926-bd0f-4929-a081-2588cc2a3d82_90x95.jpeg)
Thanks, David!
R regarding passwords — well, actually, yes — I’d prefer to store them in the KeePass.
Thanks, David!
R regarding passwords — well, actually, yes — I’d prefer to store them in the KeePass.
you can not be sure if Chrome/Chromium uses a keyring or not (without additional check from your side), so it can use the “basic” config with the Peanuts” instead of the “gnome” and generated password
better portability if you’ll want to migrate to another browser (which probably will be not able to copy passwords from you Chrome)
backup/restore KeePass database is much simpler then Crhoium’s SQLite DB + the keyring’s storage
Just a quick thought on this.