Page 1 of 1

3.2rc5 keyring

Posted: 22 Oct 2016, 14:32
by Ed_P
What are keyrings and how do I disable them? They seem to be tied to my Chrome module, google-chrome-39.0.2171.65-x86_64-1sl.xzm, and show up when I signon to a game that I play with it, which doesn't play using Firefox.

Re: 3.2rc5 keyring

Posted: 22 Oct 2016, 14:47
by Bogomips

Re: 3.2rc5 keyring

Posted: 22 Oct 2016, 16:16
by Ed_P
Bogomips wrote:Keyrings
OK but I knew it had something to do with security I just don't understand why/how it gets invoked. I don't see it when I sign on to Porteus with Firefox. And even with Chrome not activated, it's an optional thing, there is a keyring folder in /home/guest/.cache which indicates it is a 3.2 feature. Searching the Cinnamon menu for keyring or security even doesn't point to anything related to this.

Re: 3.2rc5 keyring

Posted: 22 Oct 2016, 17:54
by Bogomips

Re: 3.2rc5 keyring

Posted: 22 Oct 2016, 19:12
by Ed_P
I don't see the Chrome game signon connection.

Re: 3.2rc5 keyring

Posted: 22 Oct 2016, 20:15
by brokenman
I think you are referring to the gnome-keyring popup you get when you open chrome. I think you can disable gnome-keyring at startup. Look into the control panel 'startup' options for your desktop and see if you can disable the keyring service from starting at boot.

Re: 3.2rc5 keyring

Posted: 23 Oct 2016, 12:59
by Ed_P
brokenman wrote:I think you are referring to the gnome-keyring popup you get when you open chrome. I think you can disable gnome-keyring at startup. Look into the control panel 'startup' options for your desktop and see if you can disable the keyring service from starting at boot.
Thanks brokenman. I couldn't find anything for keyrings in Cinnamon's settings but I did disable some things in Chrome that seems to have cured the problem. See https://support.google.com/chrome/answe ... p=settings

In that Chrome is an optional module that I invoke it will be interesting to see how my changes carry over between reboots.