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 session-keyring.7
Date: Sun, 12 Mar 2023 13:18:42 +0100 [thread overview]
Message-ID: <93252839-1087-51c5-3349-bf558b3160eb@gmail.com> (raw)
In-Reply-To: <20230312045736.GB7927@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 1468 bytes --]
Hi Helge,
On 3/12/23 05:57, Helge Kreutzmann wrote:
> Hello Alex,
> On Sat, Mar 11, 2023 at 11:24:53PM +0100, Alejandro Colomar wrote:
>> On 3/11/23 18:13, Helge Kreutzmann wrote:
>>> Without further ado, the following was found:
>>>
>>> Issue: PAM → B<PAM>(7)
>>>
>>> "The session keyring is a keyring used to anchor keys on behalf of a "
>>> "process. It is typically created by B<pam_keyinit>(8) when a user logs in "
>>> "and a link will be added that refers to the B<user-keyring>(7). Optionally, "
>>> "PAM may revoke the session keyring on logout. (In typical configurations, "
>>> "PAM does do this revocation.) The session keyring has the name "
>>> "(description) I<_ses>."
>>
>> I think I prefer not doing this change, since we already have a reference
>> to PAM(7) in the SEE ALSO section, and it would clutter the description
>> to add more formatting to it. I'm doubting.
>
> Ok.
>
> Just that in HTML view, these are often turned into hyperlinks, thus
> people could easily continue reading (like in any HTML article). But I
> don't know how many people are actually doing this.
>
> (And of course knowing that PAM(7) even exists in the text is not too
> bad, either).
I decided to add a man-page reference in the first occurence.
Cheers,
Alex
>
> Greetings
>
> Helge
>
>
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-03-12 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 17:13 Issue in man page session-keyring.7 Helge Kreutzmann
2023-03-11 22:24 ` Alejandro Colomar
2023-03-12 4:57 ` Helge Kreutzmann
2023-03-12 12:18 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:08 ` G. Branden Robinson
2023-01-22 20:34 ` Helge Kreutzmann
2023-01-22 20:52 ` Alejandro Colomar
2023-01-22 20:56 ` G. Branden Robinson
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:59 ` Alejandro Colomar
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=93252839-1087-51c5-3349-bf558b3160eb@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