security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-01-21 14:47:03 +01:00
Code Activity

doc: Replace rfc0123 with RFC-0123.

Browse Source 
* doc/gpg.texi, doc/gpgsm.texi, doc/specify-user-id.texi: Fix.
This commit is contained in:
Ineiev 2016-03-04 16:34:23 +00:00 committed by NIIBE Yutaka
parent 789916281c
commit 9d2b7bff12
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/gpg.texi
View File

@ -1429,7 +1429,7 @@ Valid values for @code{name} are:
@item koi8-r
@opindex display-charset:koi8-r
The usual Russian set (rfc1489).
The usual Russian set (RFC-1489).
@item utf-8
@opindex display-charset:utf-8
@ -1656,7 +1656,7 @@ mechanisms, in the order they are to be tried:
@table @asis
@item cert
Locate a key using DNS CERT, as specified in rfc4398.
Locate a key using DNS CERT, as specified in RFC-4398.
@item pka
Locate a key using DNS PKA.

2
doc/gpgsm.texi
View File

@ -1114,7 +1114,7 @@ integer of arbitrary length. The special value @samp{random} can be
used to create a 64 bit random serial number.
@item Issuer-DN: @var{issuer-name}
This is the DN name of the issuer in rfc2253 format. If it is not set
This is the DN name of the issuer in RFC-2253 format. If it is not set
it will default to the subject DN and a special GnuPG extension will
be included in the certificate to mark it as a standalone certificate.

2
doc/specify-user-id.texi
View File

@ -111,7 +111,7 @@ escaped) RFC-2253 string
@item By exact match on the issuer's DN.
This is indicated by a leading hash mark, directly followed by a slash
and then directly followed by the rfc2253 encoded DN of the issuer.
and then directly followed by the RFC-2253 encoded DN of the issuer.
This should return the Root cert of the issuer. See note above.
@cartouche