public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page keyrings.7
Date: Sun, 4 Dec 2022 12:47:52 +0100	[thread overview]
Message-ID: <14ded556-7113-50cd-d705-942c482f09e3@gmail.com> (raw)
In-Reply-To: <20221204090709.GA32717@Debian-50-lenny-64-minimal>


[-- Attachment #1.1: Type: text/plain, Size: 2992 bytes --]

Hi Helge,

On 12/4/22 10:07, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    pinned → anchored?
> 
> "Process credentials themselves reference keyrings with specific semantics."
> "These keyrings are pinned as long as the set of credentials exists, which is"
> "usually as long as the process exists."

I'm not sure.  I see uses of both terms, and don't know the interfaces enough to 
be able to tell which term is more appropriate here.  Please CC any developers 
of those interfaces and see what they think about it.

Cheers,

Alex

---

$ grep -rn pin | grep key
man2/keyctl.2:1394:everything it pins can then be garbage collected.
man2/ioctl_getfsmap.2:57:key for which the application would like physical mapping
man2/ioctl_getfsmap.2:59:A reverse mapping key consists of the tuple (device, 
block, owner, offset).
man5/repertoiremap.5:27:The mapping section starts with the keyword
man7/user-keyring.7:26:The keyring remains pinned in existence so long as there 
are processes
man7/user-keyring.7:28:(The keyring can also be pinned indefinitely by linking it
man7/user-keyring.7:60:the last process pinning it exits.
man7/keyrings.7:232:These keyrings are pinned as long as the set of credentials 
exists,
man7/keyrings.7:614:structures that are pinning the key
man7/keyrings.7:856:NFS - User ID mapping
man7/keyrings.7:857:The NFS filesystem uses keys to store mappings of
man7/persistent-keyring.7:46:everything it pins can then be garbage collected.
man7/user-session-keyring.7:27:The keyring remains pinned in existence so long 
as there are processes
man7/user-session-keyring.7:29:(The keyring can also be pinned indefinitely by 
linking it
man7/user-session-keyring.7:63:when the last process pinning it exits.


$ grep -rn anchor | grep key
man2/add_key.2:55:.\" is consequently unlinked, then keys that it was anchoring
man7/user-keyring.7:10:The user keyring is a keyring used to anchor keys on 
behalf of a user.
man7/keyrings.7:218:it must be anchored to keep its reference count elevated
man7/keyrings.7:221:Keyrings are used to anchor other keys:
man7/keyrings.7:224:are also subject to the same anchoring requirement to prevent
man7/keyrings.7:227:The kernel makes available a number of anchor keyrings.
man7/keyrings.7:298:There are special keyrings owned by the kernel that can 
anchor keys
man7/persistent-keyring.7:10:The persistent keyring is a keyring used to anchor 
keys on behalf of a user.
man7/thread-keyring.7:10:The thread keyring is a keyring used to anchor keys on 
behalf of a process.
man7/process-keyring.7:10:The process keyring is a keyring used to anchor keys 
on behalf of a process.
man7/session-keyring.7:10:The session keyring is a keyring used to anchor keys 
on behalf of a process.
man7/user-session-keyring.7:10:The user session keyring is a keyring used to 
anchor keys on behalf of a user.


-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-04 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04  9:07 Issue in man page keyrings.7 Helge Kreutzmann
2022-12-04 11:47 ` Alejandro Colomar [this message]
2022-12-04 13:57   ` Helge Kreutzmann
2022-12-04 21:14     ` Alejandro Colomar
2022-12-05 17:13       ` Helge Kreutzmann
  -- strict thread matches above, loose matches on Subject: below --
2022-12-04  9:07 Helge Kreutzmann
2022-12-04 11:49 ` Alejandro Colomar
2022-03-13 12:34 Helge Kreutzmann

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=14ded556-7113-50cd-d705-942c482f09e3@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.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