Regenerate manual pages for OpenSSL 0.9.8p.

1 files changed, 44 insertions, 51 deletions

diff --git a/secure/usr.bin/openssl/man/rsautl.1 b/secure/usr.bin/openssl/man/rsautl.1
index f4ae4db..a2ad8e6 100644
--- a/secure/usr.bin/openssl/man/rsautl.1
+++ b/secure/usr.bin/openssl/man/rsautl.1
@@ -1,15 +1,7 @@
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.37
+.\" Automatically generated by Pod::Man 2.22 (Pod::Simple 3.07)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
-.de Sh \" Subsection heading
-.br
-.if t .Sp
-.ne 5
-.PP
-\fB\\$1\fR
-.PP
-..
 .de Sp \" Vertical space (when we can't use .PP)
 .if t .sp .5v
 .if n .sp
@@ -25,11 +17,11 @@
 ..
 .\" Set up some character translations and predefined strings.  \*(-- will
 .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
-.\" double quote, and \*(R" will give a right double quote.  | will give a
-.\" real vertical bar.  \*(C+ will give a nicer C++.  Capital omega is used to
-.\" do unbreakable dashes and therefore won't be available.  \*(C` and \*(C'
-.\" expand to `' in nroff, nothing in troff, for use with C<>.
-.tr \(*W-|\(bv\*(Tr
+.\" double quote, and \*(R" will give a right double quote.  \*(C+ will
+.\" give a nicer C++.  Capital omega is used to do unbreakable dashes and
+.\" therefore won't be available.  \*(C` and \*(C' expand to `' in nroff,
+.\" nothing in troff, for use with C<>.
+.tr \(*W-
 .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
 .ie n \{\
 .    ds -- \(*W-
@@ -48,22 +40,25 @@
 .    ds R" ''
 'br\}
 .\"
+.\" Escape single quotes in literal strings from groff's Unicode transform.
+.ie \n(.g .ds Aq \(aq
+.el       .ds Aq '
+.\"
 .\" If the F register is turned on, we'll generate index entries on stderr for
-.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
+.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
 .\" entries marked with X<> in POD.  Of course, you'll have to process the
 .\" output yourself in some meaningful fashion.
-.if \nF \{\
+.ie \nF \{\
 .    de IX
 .    tm Index:\\$1\t\\n%\t"\\$2"
 ..
 .    nr % 0
 .    rr F
 .\}
-.\"
-.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
-.\" way too many mistakes in technical documents.
-.hy 0
-.if n .na
+.el \{\
+.    de IX
+..
+.\}
 .\"
 .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
 .\" Fear.  Run.  Save yourself.  No user-serviceable parts.
@@ -129,7 +124,11 @@
 .\" ========================================================================
 .\"
 .IX Title "RSAUTL 1"
-.TH RSAUTL 1 "2010-03-24" "0.9.8n" "OpenSSL"
+.TH RSAUTL 1 "2010-11-16" "0.9.8p" "OpenSSL"
+.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
+.\" way too many mistakes in technical documents.
+.if n .ad l
+.nh
 .SH "NAME"
 rsautl \- RSA utility
 .SH "SYNOPSIS"
@@ -168,10 +167,10 @@ default.
 the input key file, by default it should be an \s-1RSA\s0 private key.
 .IP "\fB\-pubin\fR" 4
 .IX Item "-pubin"
-the input file is an \s-1RSA\s0 public key. 
+the input file is an \s-1RSA\s0 public key.
 .IP "\fB\-certin\fR" 4
 .IX Item "-certin"
-the input is a certificate containing an \s-1RSA\s0 public key. 
+the input is a certificate containing an \s-1RSA\s0 public key.
 .IP "\fB\-sign\fR" 4
 .IX Item "-sign"
 sign the input data and output the signed result. This requires
@@ -207,30 +206,28 @@ used to sign or verify small pieces of data.
 Sign some data using a private key:
 .PP
 .Vb 1
-\& openssl rsautl -sign -in file -inkey key.pem -out sig
+\& openssl rsautl \-sign \-in file \-inkey key.pem \-out sig
 .Ve
 .PP
 Recover the signed data
 .PP
 .Vb 1
-\& openssl rsautl -verify -in sig -inkey key.pem
+\& openssl rsautl \-verify \-in sig \-inkey key.pem
 .Ve
 .PP
 Examine the raw signed data:
 .PP
 .Vb 1
-\& openssl rsautl -verify -in file -inkey key.pem -raw -hexdump
-.Ve
-.PP
-.Vb 8
-\& 0000 - 00 01 ff ff ff ff ff ff-ff ff ff ff ff ff ff ff   ................
-\& 0010 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff   ................
-\& 0020 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff   ................
-\& 0030 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff   ................
-\& 0040 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff   ................
-\& 0050 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff   ................
-\& 0060 - ff ff ff ff ff ff ff ff-ff ff ff ff ff ff ff ff   ................
-\& 0070 - ff ff ff ff 00 68 65 6c-6c 6f 20 77 6f 72 6c 64   .....hello world
+\& openssl rsautl \-verify \-in file \-inkey key.pem \-raw \-hexdump
+\&
+\& 0000 \- 00 01 ff ff ff ff ff ff\-ff ff ff ff ff ff ff ff   ................
+\& 0010 \- ff ff ff ff ff ff ff ff\-ff ff ff ff ff ff ff ff   ................
+\& 0020 \- ff ff ff ff ff ff ff ff\-ff ff ff ff ff ff ff ff   ................
+\& 0030 \- ff ff ff ff ff ff ff ff\-ff ff ff ff ff ff ff ff   ................
+\& 0040 \- ff ff ff ff ff ff ff ff\-ff ff ff ff ff ff ff ff   ................
+\& 0050 \- ff ff ff ff ff ff ff ff\-ff ff ff ff ff ff ff ff   ................
+\& 0060 \- ff ff ff ff ff ff ff ff\-ff ff ff ff ff ff ff ff   ................
+\& 0070 \- ff ff ff ff 00 68 65 6c\-6c 6f 20 77 6f 72 6c 64   .....hello world
 .Ve
 .PP
 The PKCS#1 block formatting is evident from this. If this was done using
@@ -242,10 +239,8 @@ utility in conjunction with \fBasn1parse\fR. Consider the self signed
 example in certs/pca\-cert.pem . Running \fBasn1parse\fR as follows yields:
 .PP
 .Vb 1
-\& openssl asn1parse -in pca-cert.pem
-.Ve
-.PP
-.Vb 18
+\& openssl asn1parse \-in pca\-cert.pem
+\&
 \&    0:d=0  hl=4 l= 742 cons: SEQUENCE          
 \&    4:d=1  hl=4 l= 591 cons:  SEQUENCE          
 \&    8:d=2  hl=2 l=   3 cons:   cont [ 0 ]        
@@ -269,28 +264,26 @@ example in certs/pca\-cert.pem . Running \fBasn1parse\fR as follows yields:
 The final \s-1BIT\s0 \s-1STRING\s0 contains the actual signature. It can be extracted with:
 .PP
 .Vb 1
-\& openssl asn1parse -in pca-cert.pem -out sig -noout -strparse 614
+\& openssl asn1parse \-in pca\-cert.pem \-out sig \-noout \-strparse 614
 .Ve
 .PP
 The certificate public key can be extracted with:
 .PP
 .Vb 1
-\& openssl x509 -in test/testx509.pem -pubkey -noout >pubkey.pem
+\& openssl x509 \-in test/testx509.pem \-pubkey \-noout >pubkey.pem
 .Ve
 .PP
 The signature can be analysed with:
 .PP
 .Vb 1
-\& openssl rsautl -in sig -verify -asn1parse -inkey pubkey.pem -pubin
-.Ve
-.PP
-.Vb 6
+\& openssl rsautl \-in sig \-verify \-asn1parse \-inkey pubkey.pem \-pubin
+\&
 \&    0:d=0  hl=2 l=  32 cons: SEQUENCE          
 \&    2:d=1  hl=2 l=  12 cons:  SEQUENCE          
 \&    4:d=2  hl=2 l=   8 prim:   OBJECT            :md5
 \&   14:d=2  hl=2 l=   0 prim:   NULL              
 \&   16:d=1  hl=2 l=  16 prim:  OCTET STRING      
-\&      0000 - f3 46 9e aa 1a 4a 73 c9-37 ea 93 00 48 25 08 b5   .F...Js.7...H%..
+\&      0000 \- f3 46 9e aa 1a 4a 73 c9\-37 ea 93 00 48 25 08 b5   .F...Js.7...H%..
 .Ve
 .PP
 This is the parsed version of an \s-1ASN1\s0 DigestInfo structure. It can be seen that
@@ -298,13 +291,13 @@ the digest used was md5. The actual part of the certificate that was signed can
 be extracted with:
 .PP
 .Vb 1
-\& openssl asn1parse -in pca-cert.pem -out tbs -noout -strparse 4
+\& openssl asn1parse \-in pca\-cert.pem \-out tbs \-noout \-strparse 4
 .Ve
 .PP
 and its digest computed with:
 .PP
 .Vb 2
-\& openssl md5 -c tbs
+\& openssl md5 \-c tbs
 \& MD5(tbs)= f3:46:9e:aa:1a:4a:73:c9:37:ea:93:00:48:25:08:b5
 .Ve
 .PP