From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-science@gnu.org
Subject: Re: Help! I messed up guix-past
Date: Wed, 14 Sep 2022 11:31:44 +0200 [thread overview]
Message-ID: <m1fsgu5mkf.fsf@fastmail.net> (raw)
In-Reply-To: <871qsfmxoj.fsf@elephly.net>
Hi Ricardo,
> Many graphical user environments come with a key manager that unlocks
> all secrets on login. One example is Seahorse, which is used by Gnome
> to unlock the Gnome keyring on login.
And indeed, I use Gnome, although that's another element I'd really love
to get out of my life. I spend way too much time debugging Gnome/Gtk
configuration issues.
> So this would really not be about GPG doing something silly or unsafe,
> but rather about Seahorse and the Gnome keyring doing what they were
> designed to do: quietly unlocking secrets on login.
It has happened to me once that I clicked "Save password" by
accident. But that's not my current problem. I checked: the passwords
for my GPG keys are not in the login keyring.
Cheers,
Konrad
next prev parent reply other threads:[~2022-09-14 9:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:16 Help! I messed up guix-past Konrad Hinsen
2022-09-09 15:36 ` Ricardo Wurmus
2022-09-09 15:46 ` zimoun
2022-09-09 16:10 ` Konrad Hinsen
2022-09-09 17:39 ` zimoun
2022-09-10 7:39 ` Konrad Hinsen
2022-09-10 9:47 ` zimoun
2022-09-10 16:20 ` Konrad Hinsen
2022-09-11 14:07 ` Ludovic Courtès
2022-09-11 15:19 ` Efraim Flashner
2022-09-12 6:16 ` Konrad Hinsen
2022-09-12 15:26 ` Ludovic Courtès
2022-09-13 8:58 ` Konrad Hinsen
2022-09-13 9:23 ` Ricardo Wurmus
2022-09-14 9:31 ` Konrad Hinsen [this message]
2022-09-10 10:27 ` Ludovic Courtès
2022-09-10 10:40 ` zimoun
2022-09-10 14:39 ` Ricardo Wurmus
2022-09-12 16:00 ` zimoun
2022-09-09 16:16 ` Julien Lepiller
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1fsgu5mkf.fsf@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=guix-science@gnu.org \
--cc=rekado@elephly.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).