From: Matt Connell <matt@connell.tech>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring
Date: Fri, 08 Jul 2022 14:07:32 -0400 [thread overview]
Message-ID: <7ccabc08e7dadccfa267d0f8a67274c7c541c957.camel@connell.tech> (raw)
In-Reply-To: <a7974b94-852c-c06c-6c85-a7132ce10740@sys-concept.com>
On Fri, 2022-07-08 at 11:26 -0600, thelma@sys-concept.com wrote:
> - if I enter password for the keyring, how to change it in the future.
The aforementioned seahorse will allow you to manage this. I'm certain
there's a CLI way to access it.
> - do I need to keep that password, will I be ask to use the password
You'll be asked for this password whenever some application tries to
read protected secrets from the keyring, eg. Chrome, in this case.
I believe pam can be configured to allow gnome-keyring to authenticate
against your X(FCE) session login, but I've never bothered to set this
up.
> - which application application are using this keyring?
Lots of things can hook into the keyring optionally. I mentioned a
few. Chrome, Chromium, Brave, dBeaver, nheko, Evolution.
next prev parent reply other threads:[~2022-07-08 18:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 2:11 [gentoo-user] google-chrome-103.0.5060 - choose password for new keyring thelma
2022-07-08 2:23 ` Dale
2022-07-08 3:20 ` thelma
2022-07-08 3:28 ` Dale
2022-07-08 3:43 ` thelma
2022-07-08 3:50 ` Dale
2022-07-08 5:13 ` thelma
2022-07-08 6:44 ` Dale
2022-07-09 17:12 ` Wols Lists
2022-07-09 18:06 ` [gentoo-user] " Martin Vaeth
2022-07-09 21:34 ` [gentoo-user] " Neil Bothwick
2022-07-08 9:01 ` Dr Rainer Woitok
2022-07-08 9:48 ` John Covici
2022-07-08 13:34 ` Matt Connell
2022-07-08 14:02 ` Arve Barsnes
2022-07-08 16:20 ` thelma
2022-07-08 17:12 ` Neil Bothwick
2022-07-08 17:26 ` thelma
2022-07-08 18:07 ` Matt Connell [this message]
2022-07-09 17:02 ` Dr Rainer Woitok
2022-07-08 14:02 ` Matt Connell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7ccabc08e7dadccfa267d0f8a67274c7c541c957.camel@connell.tech \
--to=matt@connell.tech \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox