Package: libnss3-tools
Version: 2:3.114-1
Severity: minor
Tags: patch
* What led up to the situation?
Checking for defects with a new version
test-[g|n]roff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=10 -ww -z < "man
page"
[Use
grep -n -e ' $' -e '\\~$' -e ' \\f.$' -e ' \\"' <file>
to find (most) trailing spaces.]
["test-groff" is a script in the repository for "groff"; is not shipped]
(local copy and "troff" slightly changed by me).
[The fate of "test-nroff" was decided in groff bug #55941.]
* What was the outcome of this action?
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:349: warning: trailing space in the line
troff:<stdin>:361: warning: trailing space in the line
troff:<stdin>:363: warning: trailing space in the line
troff:<stdin>:381: warning: trailing space in the line
troff:<stdin>:382: warning: trailing space in the line
troff:<stdin>:383: warning: trailing space in the line
troff:<stdin>:384: warning: trailing space in the line
troff:<stdin>:385: warning: trailing space in the line
troff:<stdin>:386: warning: trailing space in the line
troff:<stdin>:387: warning: trailing space in the line
troff:<stdin>:388: warning: trailing space in the line
troff:<stdin>:389: warning: trailing space in the line
troff:<stdin>:390: warning: trailing space in the line
troff:<stdin>:391: warning: trailing space in the line
troff:<stdin>:392: warning: trailing space in the line
troff:<stdin>:393: warning: trailing space in the line
troff:<stdin>:394: warning: trailing space in the line
troff:<stdin>:395: warning: trailing space in the line
troff:<stdin>:396: warning: trailing space in the line
troff:<stdin>:397: warning: trailing space in the line
troff:<stdin>:398: warning: trailing space in the line
troff:<stdin>:399: warning: trailing space in the line
troff:<stdin>:400: warning: trailing space in the line
troff:<stdin>:416: warning: trailing space in the line
troff:<stdin>:417: warning: trailing space in the line
troff:<stdin>:419: warning: trailing space in the line
troff:<stdin>:428: warning: trailing space in the line
troff:<stdin>:429: warning: trailing space in the line
troff:<stdin>:431: warning: trailing space in the line
troff:<stdin>:432: warning: trailing space in the line
troff:<stdin>:433: warning: trailing space in the line
troff:<stdin>:434: warning: trailing space in the line
troff:<stdin>:435: warning: trailing space in the line
troff:<stdin>:437: warning: trailing space in the line
troff:<stdin>:438: warning: trailing space in the line
troff:<stdin>:439: warning: trailing space in the line
troff:<stdin>:440: warning: trailing space in the line
troff:<stdin>:442: warning: trailing space in the line
troff:<stdin>:476: warning: trailing space in the line
troff:<stdin>:496: warning: trailing space in the line
troff:<stdin>:508: warning: trailing space in the line
troff:<stdin>:516: warning: trailing space in the line
troff:<stdin>:520: warning: trailing space in the line
troff:<stdin>:542: warning: trailing space in the line
troff:<stdin>:543: warning: trailing space in the line
troff:<stdin>:549: warning: trailing space in the line
troff:<stdin>:551: warning: trailing space in the line
troff:<stdin>:556: warning: trailing space in the line
troff:<stdin>:557: warning: trailing space in the line
troff:<stdin>:558: warning: trailing space in the line
troff:<stdin>:566: warning: trailing space in the line
troff:<stdin>:568: warning: trailing space in the line
troff:<stdin>:573: warning: trailing space in the line
troff:<stdin>:574: warning: trailing space in the line
troff:<stdin>:575: warning: trailing space in the line
troff:<stdin>:612: warning: trailing space in the line
troff:<stdin>:626: warning: trailing space in the line
troff:<stdin>:657: warning: trailing space in the line
troff:<stdin>:723: warning: trailing space in the line
troff:<stdin>:733: warning: trailing space in the line
troff:<stdin>:735: warning: trailing space in the line
troff:<stdin>:736: warning: trailing space in the line
troff:<stdin>:737: warning: trailing space in the line
troff:<stdin>:738: warning: trailing space in the line
troff:<stdin>:739: warning: trailing space in the line
troff:<stdin>:877: warning: trailing space in the line
troff:<stdin>:879: warning: trailing space in the line
* What outcome did you expect instead?
No output (no warnings).
-.-
General remarks and further material, if a diff-file exist, are in the
attachments.
-- System Information:
Debian Release: 13.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1),
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages libnss3-tools depends on:
ii libc6 2.41-12
ii libnspr4 2:4.36-1
ii libnss3 2:3.114-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
libnss3-tools recommends no packages.
libnss3-tools suggests no packages.
-- no debconf information
Input file is modutil.1
Output from "mandoc -T lint modutil.1": (shortened list)
82 STYLE: input text line longer than 80 bytes:
10 WARNING: skipping paragraph macro: PP after SH
Find most trailing spaces with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
-.-.
Output from
test-nroff -mandoc -t -ww -z modutil.1: (shortened list)
67 line(s) with a trailing space
Find most trailing spaces with:
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
-.-.
Show if docman-to-man created this.
4:.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.-.
Remove space characters (whitespace) at the end of lines.
Use "git apply ... --whitespace=fix" to fix extra space issues, or use
global configuration "core.whitespace".
Number of lines affected is
67
-.-.
Strings longer than 3/4 of a standard line length (80).
Use "\:" to split the string at the end of an output line, for example a
long URL (web address).
This is a groff extension.
417
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
429
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
511
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
518 uri:
pkcs11:token=NSS%20Generic%20Crypto%20Services;manufacturer=Mozilla%20Foundation;serial=0000000000000000;model=NSS%203
522 uri:
pkcs11:token=NSS%20Certificate%20DB;manufacturer=Mozilla%20Foundation;serial=0000000000000000;model=NSS%203
523
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
539
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
598 name="NSS Internal PKCS #11 Module" parameters="configdir=\&. certPrefix=
keyPrefix= secmod=secmod\&.db flags=readOnly " NSS="trustOrder=75
cipherOrder=100
slotParams={0x00000001=[slotFlags=RSA,RC4,RC2,DES,DH,SHA1,MD5,MD2,SSL,TLS,AES,RANDOM
askpw=any timeout=30 ] } Flags=internal,critical"
1431 \m[blue]\fBhttp://www\&.mozilla\&.org/projects/security/pki/nss/\fR\m[]\&;.
The NSS site relates directly to NSS code changes and releases\&.
-.-.
Wrong distance (not two spaces) between sentences in the input file.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
Mark a final abbreviation point as such by suffixing it with "\&".
Some sentences (etc.) do not begin on a new line.
Split (sometimes) lines after a punctuation mark; before a conjunction.
Lines with only one (or two) space(s) between sentences could be split,
so latter sentences begin on a new line.
Use
#!/usr/bin/sh
sed -e '/^\./n' \
-e 's/\([[:alpha:]]\)\. */\1.\n/g' $1
to split lines after a sentence period.
Check result with the difference between the formatted outputs.
See also the attachment "general.bugs"
[List of affected lines removed.]
-.-.
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
Add "\:" to split the string for the output, "\<newline>" in the source.
[List of affected lines removed.]
-.-.
Put a parenthetical sentence, phrase on a separate line,
if not part of a code.
See man-pages(7), item "semantic newline".
[List of affected lines removed.]
modutil.1:53:always requires one (and only one) option to specify the type of
module operation\&. Each option may take arguments, anywhere from none to
multiple arguments\&.
modutil.1:234:supports several mechanisms: RSA, DSA, RC2, RC4, RC5, AES, DES,
DH, SHA1, SHA256, SHA512, SSL, TLS, MD5, MD2, RANDOM (for random number
generation), and FRIENDLY (meaning certificates are publicly readable)\&.
modutil.1:563: Login Type: Public (no login required)
modutil.1:606:Multiple security modules may provide support for the same
security mechanisms\&. It is possible to set a specific security module as the
default provider for a specific security mechanism (or, conversely, to prohibit
a provider from supplying those mechanisms)\&.
modutil.1:701:command with either a true or false flag (it doesn\*(Aqt matter
which)\&. The tool returns the current FIPS setting\&.
modutil.1:885:Quotes and backslashes must be escaped with a backslash\&. A
complex string must not include newlines or carriage returns\&.Outside of
complex strings, all white space (for example, spaces, tabs, and carriage
returns) is considered equal and is used only to delimit tokens\&.
modutil.1:963:LINUX (ppc, alpha, x86)
modutil.1:1196:specifies ciphers that this module provides that NSS does not
provide (so that the module enables those ciphers for NSS)\&. This is
equivalent to the
modutil.1:1229:is to hold executable files (such as setup programs) or files
that are used by these programs\&. Files destined for the temporary directory
are guaranteed to be in place before any executable file is run; they are not
deleted until all executable files have finished\&.
modutil.1:1430:For information about NSS and other tools related to NSS (like
JSS), check out the NSS project wiki at
-.-.
Use a character "\(->" instead of plain "->" or "\->".
862:\-\-> valuelist
864:valuelist \-\-> value valuelist
867:value \-\-\-> key_value_pair
870:key_value_pair \-\-> key { valuelist }
872:key \-\-> string
874:string \-\-> simple_string
877:simple_string \-\-> [^ \et\en\e""{""}"]+
879:complex_string \-\-> ([^\e"\e\e\er\en]|(\e\e\e")|(\e\e\e\e))+
-.-.
No need for '\&' to be in front of a period (.),
if there is a character in front of it.
Remove with "sed -e 's/\(.\)\\&\./\1./g'".
[List of affected lines removed.]
-.-.
Only one space character is after a possible end of sentence
(after a punctuation, that can end a sentence).
[List of affected lines removed.]
-.-.
Remove quotes when there is a printable
but no space character between them
and the quotes are not for emphasis (markup),
for example as an argument to a macro.
modutil.1:3:.\" Author: [see the "Authors" section]
modutil.1:10:.TH "MODUTIL" "1" "19 May 2021" "nss-tools" "NSS Security Tools"
modutil.1:30:.SH "NAME"
modutil.1:32:.SH "SYNOPSIS"
modutil.1:35:.SH "STATUS"
modutil.1:39:.SH "DESCRIPTION"
modutil.1:49:.SH "OPTIONS"
modutil.1:1436:.SH "AUTHORS"
modutil.1:1441:.SH "LICENSE"
modutil.1:1444:.SH "NOTES"
-.-.
Remove excessive "\&" when it has no functional purpose.
38:\m[blue]\fBMozilla NSS bug 836477\fR\m[]\&\s-2\u[1]\d\s+2
-.-.
Use "\-" instead of "-" in web addresses.
16:.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
-.-.
Put a (long) web address on a new output line to reduce the posibility of
splitting the address between two output lines.
Or inhibit hyphenation with "\%" in front of the name.
1382:https://wiki\&.mozilla\&.org/NSS_Shared_DB_Howto
1395:https://wiki\&.mozilla\&.org/NSS_Shared_DB
1415:https://wiki\&.mozilla\&.org/NSS_Shared_DB_Howto
1426:https://wiki\&.mozilla\&.org/NSS_Shared_DB
1431:\m[blue]\fBhttp://www\&.mozilla\&.org/projects/security/pki/nss/\fR\m[]\&;.
The NSS site relates directly to NSS code changes and releases\&.
1433:Mailing lists: https://lists\&.mozilla\&.org/listinfo/dev\-tech\-crypto
1443:Licensed under the Mozilla Public License, v\&. 2\&.0\&. If a copy of the
MPL was not distributed with this file, You can obtain one at
http://mozilla\&.org/MPL/2\&.0/\&;.
1448:\%https://bugzilla.mozilla.org/show_bug.cgi?id=836477
-.-.
Output from "test-groff -mandoc -t -K utf8 -rF0 -rHY=0 -rCHECKSTYLE=0 -ww -z ":
troff:<stdin>:349: warning: trailing space in the line
troff:<stdin>:361: warning: trailing space in the line
troff:<stdin>:363: warning: trailing space in the line
troff:<stdin>:381: warning: trailing space in the line
troff:<stdin>:382: warning: trailing space in the line
troff:<stdin>:383: warning: trailing space in the line
troff:<stdin>:384: warning: trailing space in the line
troff:<stdin>:385: warning: trailing space in the line
troff:<stdin>:386: warning: trailing space in the line
troff:<stdin>:387: warning: trailing space in the line
troff:<stdin>:388: warning: trailing space in the line
troff:<stdin>:389: warning: trailing space in the line
troff:<stdin>:390: warning: trailing space in the line
troff:<stdin>:391: warning: trailing space in the line
troff:<stdin>:392: warning: trailing space in the line
troff:<stdin>:393: warning: trailing space in the line
troff:<stdin>:394: warning: trailing space in the line
troff:<stdin>:395: warning: trailing space in the line
troff:<stdin>:396: warning: trailing space in the line
troff:<stdin>:397: warning: trailing space in the line
troff:<stdin>:398: warning: trailing space in the line
troff:<stdin>:399: warning: trailing space in the line
troff:<stdin>:400: warning: trailing space in the line
troff:<stdin>:416: warning: trailing space in the line
troff:<stdin>:417: warning: trailing space in the line
troff:<stdin>:419: warning: trailing space in the line
troff:<stdin>:428: warning: trailing space in the line
troff:<stdin>:429: warning: trailing space in the line
troff:<stdin>:431: warning: trailing space in the line
troff:<stdin>:432: warning: trailing space in the line
troff:<stdin>:433: warning: trailing space in the line
troff:<stdin>:434: warning: trailing space in the line
troff:<stdin>:435: warning: trailing space in the line
troff:<stdin>:437: warning: trailing space in the line
troff:<stdin>:438: warning: trailing space in the line
troff:<stdin>:439: warning: trailing space in the line
troff:<stdin>:440: warning: trailing space in the line
troff:<stdin>:442: warning: trailing space in the line
troff:<stdin>:476: warning: trailing space in the line
troff:<stdin>:496: warning: trailing space in the line
troff:<stdin>:508: warning: trailing space in the line
troff:<stdin>:516: warning: trailing space in the line
troff:<stdin>:520: warning: trailing space in the line
troff:<stdin>:542: warning: trailing space in the line
troff:<stdin>:543: warning: trailing space in the line
troff:<stdin>:549: warning: trailing space in the line
troff:<stdin>:551: warning: trailing space in the line
troff:<stdin>:556: warning: trailing space in the line
troff:<stdin>:557: warning: trailing space in the line
troff:<stdin>:558: warning: trailing space in the line
troff:<stdin>:566: warning: trailing space in the line
troff:<stdin>:568: warning: trailing space in the line
troff:<stdin>:573: warning: trailing space in the line
troff:<stdin>:574: warning: trailing space in the line
troff:<stdin>:575: warning: trailing space in the line
troff:<stdin>:612: warning: trailing space in the line
troff:<stdin>:626: warning: trailing space in the line
troff:<stdin>:657: warning: trailing space in the line
troff:<stdin>:723: warning: trailing space in the line
troff:<stdin>:733: warning: trailing space in the line
troff:<stdin>:735: warning: trailing space in the line
troff:<stdin>:736: warning: trailing space in the line
troff:<stdin>:737: warning: trailing space in the line
troff:<stdin>:738: warning: trailing space in the line
troff:<stdin>:739: warning: trailing space in the line
troff:<stdin>:877: warning: trailing space in the line
troff:<stdin>:879: warning: trailing space in the line
-.-
Generally:
Split (sometimes) lines after a punctuation mark; before a conjunction.
--- modutil.1 2025-08-13 23:19:36.729047135 +0000
+++ modutil.1.new 2025-08-13 23:22:16.017567269 +0000
@@ -346,7 +346,7 @@ directly or by running a JAR file and in
.RS 4
.\}
.nf
-modutil \-add modulename \-libfile library\-file [\-ciphers
cipher\-enable\-list] [\-mechanisms mechanism\-list]
+modutil \-add modulename \-libfile library\-file [\-ciphers
cipher\-enable\-list] [\-mechanisms mechanism\-list]
.fi
.if n \{\
.RE
@@ -358,9 +358,9 @@ For example:
.RS 4
.\}
.nf
-modutil \-dbdir /home/my/sharednssdb \-add "Example PKCS #11 Module" \-libfile
"/tmp/crypto\&.so" \-mechanisms RSA:DSA:RC2:RANDOM
+modutil \-dbdir /home/my/sharednssdb \-add "Example PKCS #11 Module" \-libfile
"/tmp/crypto\&.so" \-mechanisms RSA:DSA:RC2:RANDOM
-Using database directory \&.\&.\&.
+Using database directory \&.\&.\&.
Module "Example PKCS #11 Module" added to database\&.
.fi
.if n \{\
@@ -378,26 +378,26 @@ The JAR installation script defines the
.RS 4
.\}
.nf
-Platforms {
- Linux:5\&.4\&.08:x86 {
- ModuleName { "Example PKCS #11 Module" }
- ModuleFile { crypto\&.so }
- DefaultMechanismFlags{0x0000}
- CipherEnableFlags{0x0000}
- Files {
- crypto\&.so {
- Path{ /tmp/crypto\&.so }
- }
- setup\&.sh {
- Executable
- Path{ /tmp/setup\&.sh }
- }
- }
- }
- Linux:6\&.0\&.0:x86 {
- EquivalentPlatform { Linux:5\&.4\&.08:x86 }
- }
-}
+Platforms {
+ Linux:5\&.4\&.08:x86 {
+ ModuleName { "Example PKCS #11 Module" }
+ ModuleFile { crypto\&.so }
+ DefaultMechanismFlags{0x0000}
+ CipherEnableFlags{0x0000}
+ Files {
+ crypto\&.so {
+ Path{ /tmp/crypto\&.so }
+ }
+ setup\&.sh {
+ Executable
+ Path{ /tmp/setup\&.sh }
+ }
+ }
+ }
+ Linux:6\&.0\&.0:x86 {
+ EquivalentPlatform { Linux:5\&.4\&.08:x86 }
+ }
+}
.fi
.if n \{\
.RE
@@ -413,10 +413,10 @@ argument\&.
.nf
modutil \-dbdir /home/mt"jar\-install\-filey/sharednssdb \-jar install\&.jar
\-installdir /home/my/sharednssdb
-This installation JAR file was signed by:
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+This installation JAR file was signed by:
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-**SUBJECT NAME**
+**SUBJECT NAME**
C=US, ST=California, L=Mountain View, CN=Cryptorific Inc\&., OU=Digital ID
Class 3 \- Netscape Object Signing, OU="www\&.verisign\&.com/repository/CPS
@@ -425,21 +425,21 @@ Incorp\&. by Ref\&.,LIAB\&.LTD(c)9 6", O
Organization, OU="VeriSign, Inc\&.", O=VeriSign Trust Network **ISSUER
NAME**, OU=www\&.verisign\&.com/CPS Incorp\&.by Ref\&. LIABILITY LTD\&.(c)97
VeriSign, OU=VeriSign Object Signing CA \- Class 3 Organization,
-OU="VeriSign, Inc\&.", O=VeriSign Trust Network
-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+OU="VeriSign, Inc\&.", O=VeriSign Trust Network
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-Do you wish to continue this installation? (y/n) y
-Using installer script "installer_script"
-Successfully parsed installation script
-Current platform is Linux:5\&.4\&.08:x86
-Using installation parameters for platform Linux:5\&.4\&.08:x86
+Do you wish to continue this installation? (y/n) y
+Using installer script "installer_script"
+Successfully parsed installation script
+Current platform is Linux:5\&.4\&.08:x86
+Using installation parameters for platform Linux:5\&.4\&.08:x86
Installed file crypto\&.so to /tmp/crypto\&.so
-Installed file setup\&.sh to \&./pk11inst\&.dir/setup\&.sh
-Executing "\&./pk11inst\&.dir/setup\&.sh"\&.\&.\&.
-"\&./pk11inst\&.dir/setup\&.sh" executed successfully
-Installed module "Example PKCS #11 Module" into module database
+Installed file setup\&.sh to \&./pk11inst\&.dir/setup\&.sh
+Executing "\&./pk11inst\&.dir/setup\&.sh"\&.\&.\&.
+"\&./pk11inst\&.dir/setup\&.sh" executed successfully
+Installed module "Example PKCS #11 Module" into module database
-Installation completed successfully
+Installation completed successfully
.fi
.if n \{\
.RE
@@ -473,7 +473,7 @@ database:
.RS 4
.\}
.nf
-modutil \-delete modulename \-dbdir directory
+modutil \-delete modulename \-dbdir directory
.fi
.if n \{\
.RE
@@ -493,7 +493,7 @@ command\&.
.RS 4
.\}
.nf
-modutil \-list [modulename] \-dbdir directory
+modutil \-list [modulename] \-dbdir directory
.fi
.if n \{\
.RE
@@ -505,7 +505,7 @@ Listing the modules shows the module nam
.RS 4
.\}
.nf
-modutil \-list \-dbdir /home/my/sharednssdb
+modutil \-list \-dbdir /home/my/sharednssdb
Listing of PKCS #11 Modules
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
@@ -513,11 +513,11 @@ Listing of PKCS #11 Modules
slots: 2 slots attached
status: loaded
- slot: NSS Internal Cryptographic Services
+ slot: NSS Internal Cryptographic Services
token: NSS Generic Crypto Services
uri:
pkcs11:token=NSS%20Generic%20Crypto%20Services;manufacturer=Mozilla%20Foundation;serial=0000000000000000;model=NSS%203
- slot: NSS User Private Key and Certificate Services
+ slot: NSS User Private Key and Certificate Services
token: NSS Certificate DB
uri:
pkcs11:token=NSS%20Certificate%20DB;manufacturer=Mozilla%20Foundation;serial=0000000000000000;model=NSS%203
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
@@ -539,23 +539,23 @@ returns details information about the mo
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
Name: NSS Internal PKCS #11 Module
Library file: **Internal ONLY module**
-Manufacturer: Mozilla Foundation
-Description: NSS Internal Crypto Services
+Manufacturer: Mozilla Foundation
+Description: NSS Internal Crypto Services
PKCS #11 Version 2\&.20
Library Version: 3\&.11
Cipher Enable Flags: None
Default Mechanism Flags: RSA:RC2:RC4:DES:DH:SHA1:MD5:MD2:SSL:TLS:AES
- Slot: NSS Internal Cryptographic Services
+ Slot: NSS Internal Cryptographic Services
Slot Mechanism Flags: RSA:RC2:RC4:DES:DH:SHA1:MD5:MD2:SSL:TLS:AES
- Manufacturer: Mozilla Foundation
+ Manufacturer: Mozilla Foundation
Type: Software
Version Number: 3\&.11
Firmware Version: 0\&.0
Status: Enabled
- Token Name: NSS Generic Crypto Services
- Token Manufacturer: Mozilla Foundation
- Token Model: NSS 3
+ Token Name: NSS Generic Crypto Services
+ Token Manufacturer: Mozilla Foundation
+ Token Model: NSS 3
Token Serial Number: 0000000000000000
Token Version: 4\&.0
Token Firmware Version: 0\&.0
@@ -563,16 +563,16 @@ Default Mechanism Flags: RSA:RC2:RC4:DES
Login Type: Public (no login required)
User Pin: NOT Initialized
- Slot: NSS User Private Key and Certificate Services
+ Slot: NSS User Private Key and Certificate Services
Slot Mechanism Flags: None
- Manufacturer: Mozilla Foundation
+ Manufacturer: Mozilla Foundation
Type: Software
Version Number: 3\&.11
Firmware Version: 0\&.0
Status: Enabled
- Token Name: NSS Certificate DB
- Token Manufacturer: Mozilla Foundation
- Token Model: NSS 3
+ Token Name: NSS Certificate DB
+ Token Manufacturer: Mozilla Foundation
+ Token Model: NSS 3
Token Serial Number: 0000000000000000
Token Version: 8\&.3
Token Firmware Version: 0\&.0
@@ -609,7 +609,7 @@ Multiple security modules may provide su
.RS 4
.\}
.nf
-modutil \-default modulename \-mechanisms mechanism\-list
+modutil \-default modulename \-mechanisms mechanism\-list
.fi
.if n \{\
.RE
@@ -623,7 +623,7 @@ command with a colon\-separated list of
.RS 4
.\}
.nf
-modutil \-default "NSS Internal PKCS #11 Module" \-dbdir \-mechanisms
RSA:DSA:RC2
+modutil \-default "NSS Internal PKCS #11 Module" \-dbdir \-mechanisms
RSA:DSA:RC2
Using database directory c:\edatabases\&.\&.\&.
@@ -654,7 +654,7 @@ Modules, and specific slots on modules,
.RS 4
.\}
.nf
-modutil \-enable|\-disable modulename [\-slot slotname]
+modutil \-enable|\-disable modulename [\-slot slotname]
.fi
.if n \{\
.RE
@@ -720,7 +720,7 @@ Initializing or changing a token\*(Aqs p
.RS 4
.\}
.nf
-modutil \-changepw tokenname [\-pwfile old\-password\-file] [\-newpwfile
new\-password\-file]
+modutil \-changepw tokenname [\-pwfile old\-password\-file] [\-newpwfile
new\-password\-file]
.fi
.if n \{\
.RE
@@ -730,13 +730,13 @@ modutil \-changepw tokenname [\-pwfile o
.RS 4
.\}
.nf
-modutil \-dbdir /home/my/sharednssdb \-changepw "NSS Certificate DB"
+modutil \-dbdir /home/my/sharednssdb \-changepw "NSS Certificate DB"
-Enter old password:
-Incorrect password, try again\&.\&.\&.
-Enter old password:
-Enter new password:
-Re\-enter new password:
+Enter old password:
+Incorrect password, try again\&.\&.\&.
+Enter old password:
+Enter new password:
+Re\-enter new password:
Token "Communicator Certificate DB" password changed successfully\&.
.fi
.if n \{\
@@ -874,9 +874,9 @@ key \-\-> string
string \-\-> simple_string
"complex_string"
-simple_string \-\-> [^ \et\en\e""{""}"]+
+simple_string \-\-> [^ \et\en\e""{""}"]+
-complex_string \-\-> ([^\e"\e\e\er\en]|(\e\e\e")|(\e\e\e\e))+
+complex_string \-\-> ([^\e"\e\e\er\en]|(\e\e\e")|(\e\e\e\e))+
.fi
.if n \{\
.RE
Any program (person), that produces man pages, should check the output
for defects by using (both groff and nroff)
[gn]roff -mandoc -t -ww -b -z -K utf8 <man page>
To find trailing space use
grep -n -e ' $' -e ' \\f.$' -e ' \\"' <man page>
The same goes for man pages that are used as an input.
-.-
For a style guide use
mandoc -T lint
-.-
For general input conventions consult the man page "nroff(7)" (item
"Input conventions") or the Texinfo manual about the same item.
-.-
Any "autogenerator" should check its products with the above mentioned
'groff', 'mandoc', and additionally with 'nroff ...'.
It should also check its input files for too long (> 80) lines.
This is just a simple quality control measure.
The "autogenerator" may have to be corrected to get a better man page,
the source file may, and any additional file may.
Common defects:
Not removing trailing spaces (in in- and output).
The reason for these trailing spaces should be found and eliminated.
"git" has a "tool" to point out whitespace,
see for example "git-apply(1)" and git-config(1)")
Not beginning each input sentence on a new line.
Line length and patch size should thus be reduced.
The script "reportbug" uses 'quoted-printable' encoding when a line is
longer than 1024 characters in an 'ascii' file.
See man-pages(7), item "semantic newline".
-.-
The difference between the formatted output of the original
and patched file can be seen with:
nroff -mandoc <file1> > <out1>
nroff -mandoc <file2> > <out2>
diff -d -u <out1> <out2>
and for groff, using
\"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -mandoc -Z - \"
instead of 'nroff -mandoc'
Add the option '-t', if the file contains a table.
Read the output from 'diff -d -u ...' with 'less -R' or similar.
-.-.
If 'man' (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -b -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-
