rpc.tlsservd.8: Fix the RFC number now that it exists
The RFC for this finally got published and, therefore, now has a number. This patch puts this RFC number in the man page. This is a content change. MFC after: 1 week
This commit is contained in:
parent
8b43388c74
commit
423387bee2
@ -26,7 +26,7 @@
|
||||
.\" $FreeBSD$
|
||||
.\"
|
||||
.\" Modified from gssd.8 for rpc.tlsservd.8 by Rick Macklem.
|
||||
.Dd May 22, 2022
|
||||
.Dd September 23, 2022
|
||||
.Dt RPC.TLSSERVD 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -303,7 +303,7 @@ and either the
|
||||
or
|
||||
.Fl p
|
||||
options.
|
||||
Use of this option might not conform to RFC-NNNN, which does
|
||||
Use of this option might not conform to RFC-9289, which does
|
||||
not allow certificates to be used for user authentication.
|
||||
.It Fl v , Fl Fl verbose
|
||||
Run in verbose mode.
|
||||
@ -361,7 +361,7 @@ options is allowed.
|
||||
.Sh STANDARDS
|
||||
The implementation is based on the specification in
|
||||
.Rs
|
||||
.%B "RFC NNNN"
|
||||
.%B "RFC 9289"
|
||||
.%T "Towards Remote Procedure Call Encryption By Default"
|
||||
.Re
|
||||
.Sh HISTORY
|
||||
|
Loading…
Reference in New Issue
Block a user