Page 7 of 13

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 8:55 am
by Eadwine Rose
I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 9:05 am
by richb
Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
On first opening with Google Chrome, I am always asked for the keyring password.

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 9:09 am
by fehlix
j2mcgreg wrote: Mon Dec 17, 2018 10:24 pm I'm getting this in Chrome "Enter password to unlock your login keyring", which would be fine except there was no initial prompt to set up a password.
When you log-in the first time with your normal username and password, during the log-in process a new login-keyring is (shall be) generated automatically by "libpam-gnomekeyring", if not already existing. As protecting password used for this keyring the user's password is used. After login this keyring is automatically unlocked. You can check this by doing the following:
- close all programs like Chrome etc
- clear/remove all existing keyrings

Code: Select all

rm ~/.local/share/keyrings/*
- logout and login
- dont' start Chrome
- open Password and Keys from the Menu
and you'll find a unlocked login-keyring as indicated by the unlocked symbol:
Password-and-keys-login-keyring.png
When you now open Chromium or any other app requiring access to use the keyring,
you will/shall not see any prompt.

If this showing of a password-prompt for unlocking thy keyring happens again, we might have a timing issues during the log-in process.
In that case please do this:
First clear again as described above the keyring.
Next do open Settings -> Application Autostart and click to enable on "Secret Storage Service "GNOME-keyring"
This might fix the timing related issue, if not please report back here.
:puppy:

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 9:09 am
by Eadwine Rose
richb wrote: Tue Dec 18, 2018 9:05 am
Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
On first opening with Google Chrome, I am always asked for the keyring password.
Not here.. *shrug*

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 9:11 am
by richb
I like the extra security.

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 9:12 am
by fehlix
Eadwine Rose wrote: Tue Dec 18, 2018 8:55 am I have never been asked for a master password or a keyring password for Chrome. Been using it for quite a long time now :)
B/c you used an empty password for the keyring, I assume. (Which we shall not advocate to the user, but instead use (and fix if not working) a more secure solution)

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 9:16 am
by Eadwine Rose
I cannot even remember EVER getting a keyring question for Chrome. I have gotten the question for skype IIRC, but Chrome? Never.

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 10:16 am
by j2mcgreg
j2mcgreg wrote: Mon Dec 17, 2018 11:24 pm dolphin_oracle wrote:
it should be just your user password.
It wouldn't accept it. In any event, I reinstalled RC1 and chose Chromium instead of Chrome and declined Google's offer to sync all my devices. I want to see if the problem recurs.
Immediately after the reinstall, chromium worked fine with no appearance of the key ring prompt. However, it did reappear after these two packages:

Code: Select all

ecryptfs-utils (111-4), and, libecryptfs1 (111-4)
were installed after an update. So far, the prompt is accepting my normal password.

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 10:24 am
by fehlix
j2mcgreg wrote: Tue Dec 18, 2018 10:16 am
j2mcgreg wrote: Mon Dec 17, 2018 11:24 pm dolphin_oracle wrote:
it should be just your user password.
It wouldn't accept it. In any event, I reinstalled RC1 and chose Chromium instead of Chrome and declined Google's offer to sync all my devices. I want to see if the problem recurs.
Immediately after the reinstall, chromium worked fine with no appearance of the key ring prompt. However, it did reappear after these two packages:

Code: Select all

ecryptfs-utils (111-4), and, libecryptfs1 (111-4)
were installed after an update. So far, the prompt is accepting my normal password.
Would enabling "Secret Storage Service GNOME-keyring" in autostart, as mentioned in the prvious post solve password prompt issue.

Re: MX-18 RC1 Feedback

Posted: Tue Dec 18, 2018 10:53 am
by richb
Not sure what this means so do not blindly change. In Google Chrome, "chrome://flags/", invoked by typing in address bar, There is this entry:
Migrate passwords to "Login Data"
Performs a one-off irreversible migration of passwords from the gnome-keyring or kwallet into the profile directory. – Linux
The options are default, enable, disable with default as installed choice.