Gnome-keyring - unlocked

[Real]

So just deleting everything when confused works huh? I'm about to pull the trigger on a nas device myself so this will help I'm sure. Thanks Lilberty

[S.t.e.P.]

forgot to backup the "keyrings" folder before the MX21 update. It seems this bug is still in Seahorse. For over an hour now I'm trying to get the password for this forum saved in Vivaldi, but after logout from MX it is gone. I tried all the descriptions here in this thread through and through and it doesn't save it.
Can one remove Seahorse in Synaptics and use just another Password Manager? Slowly it's driving me nuts.

[ganeshmallyap]

I use pass (the standard UNIX password manager) and its extensions. I found it quite secure, data is stored after encryption. Passwords can be synced with git hub using SSH keys securely. Linux/Mac/Windows/Android/IOS platforms support this either directly or through extensions both at browser and OS level. If used through github, then data on all devices will remain in sync by using pull and push operation from git. At a overall level i am quite contended with this option. For more information please visit https://www.passwordstore.org/.

[germany]

I used to be able to simply add this:
--password-store=basic %U
behind every startup command for the three web browsers which I'm using. As of the latest MX 23.4 Libretto that no longer works. At first I thought it was just Chrome until I noticed that that addition to the startup command no longer appears to work on any web browser. The solution at the beginning of this thread worked for me though. Haven't rebooted yet to see if the change sticks permanently.
Shouldn't there be some way of utilizing about:config in a web browser, in order to not require the password during startup?

[germany]

Well the instructions on the first page work ..... but only until the machine is rebooted. At that point that message about entering the password when you access the web browser appears again. I'm seeing this on all three browsers that I have in use, Chrome, Firefox, and Edge. Isn't there some way to just disable that once and for all, permanently?

[fehlix]

Well the instructions on the first page work ..... but only until the machine is rebooted.

Instructions can be read and interpreted differently, better tell the steps you have done.

At that point that message about entering the password when you access the web browser appears again. I'm seeing this on all three browsers that I have in use, Chrome, Firefox, and Edge. Isn't there some way to just disable that once and for all, permanently?

Perhaps, this way:
* first reset all what was done, and by this verify/confirm that's really the gnome-keyring, and nothing else,
e.g this way:
** remove/ reset keying and disable autologin
- first disable autologin, e.g. with help of "MX User Manager" tool
- close all applications /browser
- open terminal and remove existing gnome-keyring:

Code: Select all

rm ~/.local/share/keyrings/*

- reboot

Code: Select all

sudo reboot

You should now have login screen, where you enter the user password to login.
Now a new gnome-keyring would have been created and already unlocked, ready to work
with any app requiring access to the keyring.
If you still get a password prompt, than something else is causing the issue.

[germany]

Well the instructions on the first page work ..... but only until the machine is rebooted.

Instructions can be read and interpreted differently, better tell the steps you have done.

No, those instructions along with the visual guide can't possibly be interpreted differently. I found out what caused the issue. For some reason I have the default keyring but then there's also the standard keyring. When I went ahead and repeated the process on the standard keyring everything was fine. I've now rebooted three times and was able to open the web-browsers without any issues. Thanks for the information though, fehlix. I will make a note of that for the future.

.

[fehlix]

Well the instructions on the first page work ..... but only until the machine is rebooted.

Instructions can be read and interpreted differently, better tell the steps you have done.

No, those instructions along with the visual guide can't possibly be interpreted differently.

You missed the point, reporting the steps done would have helped me to see what you have done,
in order to get a clear picture of the issue.

I found out what caused the issue. For some reason I have the default keyring but then there's also the standard keyring.

Yes, without an existing login-keyring a new "default" keyring will be created when app requesting access to a keyring
in order to store their stuff. Somehow I thought that was explained with the early posts.
To get additional default keyring unlocked at login, the system offers to place the unlocking password of
the default keyring into the login keyring, when login keyring would have been unlocked at login.
Note: IIRC, it helped me to understand whats going on, by checking with help of seahorse tool (Password & Keys) the keyring status.

[germany]

You missed the point, reporting the steps done would have helped me to see what you have done,
in order to get a clear picture of the issue.

I did exactly as directed, by opening the keyring app, then selecting the default keyring with a right click, followed by changing the password / leaving both password fields blank, closing the application, and finally testing with a reboot if the web browsers are now working without the unlocking keyring request .... which they did.

.

[fehlix]

You missed the point, reporting the steps done would have helped me to see what you have done,
in order to get a clear picture of the issue.

I did exactly as directed, by opening the keyring app, then selecting the default keyring with a right click, followed by changing the password / leaving both password fields blank, closing the application, and finally testing with a reboot if the web browsers are now working without the unlocking keyring request .... which they did.

That's not really what I do recommend:
Leaving the keyring with an unprotected empty password open, is a security issue,
b/c any bad websites, which are smart enough, can now read any "secretes" googl's chromium would rather protect from not getting stolen.
But to each his own. Not my recommendation, b/c of a potetial security risk.
My recommendation is to keep a password for both login and defaul keyring.
and do disable autologin. So that at login the keyring and the default keyring (if separate) get unlocked,
and stays protected.