From: markus.suvanto@gmail.com
To: David Howells <dhowells@redhat.com>
Cc: Marc Dionne <marc.dionne@auristor.com>,
linux-afs@lists.infradead.org, keyrings@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] afs: Fix dynamic root interaction with failing DNS lookups
Date: Tue, 12 Dec 2023 11:57:04 +0200 [thread overview]
Message-ID: <37bed7ea3e57c4a2d8de5a20b327f6fdd7c79677.camel@gmail.com> (raw)
In-Reply-To: <2812152.1702374569@warthog.procyon.org.uk>
> > masu@t470 ~ % grep rxrpc /proc/keys
> > 23e16cda I--Q--- 1 3d 3b010000 1001 100 rxrpc afs@movesole.com: ka
>
> Okay, I see the persistent keyring disappear, but I don't see a key linked
> into my session keyring vanish.
Full log of my commands...
masu@t470 ~ % klist
klist: Credentials cache keyring 'persistent:1001:1001' not found
masu@t470 ~ % keyctl show
Session Keyring
388545754 --alswrv 1001 65534 keyring: _uid_ses.1001
946177719 --alswrv 1001 65534 \_ keyring: _uid.1001
masu@t470 ~ % grep rxrpc /proc/keys
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ % kinit masu@MOVESOLE.COM
Password for masu@MOVESOLE.COM:
masu@t470 ~ % aklog-kafs-kdf movesole.com MOVESOLE.COM
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ % grep rxrpc /proc/keys
2600d2d5 I--Q--- 1 3d 3b010000 1001 100 rxrpc afs@movesole.com: ka
masu@t470 ~ % klist
Ticket cache: KEYRING:persistent:1001:1001
Default principal: masu@MOVESOLE.COM
Valid starting Expires Service principal
12.12.2023 11.52.47 16.12.2023 11.52.40 afs/movesole.com@MOVESOLE.COM
renew until 26.12.2023 11.52.40
12.12.2023 11.52.43 16.12.2023 11.52.40 krbtgt/MOVESOLE.COM@MOVESOLE.COM
renew until 26.12.2023 11.52.40
masu@t470 ~ % keyctl show
Session Keyring
388545754 --alswrv 1001 65534 keyring: _uid_ses.1001
946177719 --alswrv 1001 65534 \_ keyring: _uid.1001
637588181 --als-rv 1001 100 \_ rxrpc: afs@movesole.com
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ % ls /afs/notfound
ls: tiedostoa '/afs/notfound' ei voi käsitellä: Tiedostoa tai hakemistoa ei ole
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ %
masu@t470 ~ % klist
klist: Credentials cache keyring 'persistent:1001:1001' not found
masu@t470 ~ % grep rxrpc /proc/keys
masu@t470 ~ % keyctl show
Session Keyring
1025218481 --alswrv 1001 65534 keyring: _uid_ses.1001
322736164 --alswrv 1001 65534 \_ keyring: _uid.1001
prev parent reply other threads:[~2023-12-12 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 16:34 [PATCH 0/3] afs: Fix dynamic root interaction with failing DNS lookups David Howells
2023-12-11 16:34 ` [PATCH 1/3] afs: Fix the dynamic root's d_delete to always delete unused dentries David Howells
2023-12-11 16:34 ` [PATCH 2/3] afs: Fix dynamic root lookup DNS check David Howells
2023-12-11 17:37 ` Marc Dionne
2023-12-11 16:34 ` [PATCH 3/3] keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry David Howells
2023-12-11 16:40 ` [PATCH 0/3] afs: Fix dynamic root interaction with failing DNS lookups David Howells
2023-12-11 21:33 ` markus.suvanto
2023-12-12 9:03 ` David Howells
2023-12-12 9:41 ` markus.suvanto
2023-12-12 9:49 ` David Howells
2023-12-12 9:57 ` markus.suvanto [this message]
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=37bed7ea3e57c4a2d8de5a20b327f6fdd7c79677.camel@gmail.com \
--to=markus.suvanto@gmail.com \
--cc=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
/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).