aboutsummaryrefslogtreecommitdiff
path: root/man/man1/pem.1
diff options
context:
space:
mode:
authorrsc <devnull@localhost>2005-02-13 23:44:12 +0000
committerrsc <devnull@localhost>2005-02-13 23:44:12 +0000
commit30f6ae144c291409de3657c4bbbaf4983a516772 (patch)
tree53b622d39d6677695587bec654dcd65e867a9656 /man/man1/pem.1
parent3170c7d40bbdc19cdd2321a0bde7cdab3be526da (diff)
downloadplan9port-30f6ae144c291409de3657c4bbbaf4983a516772.tar.gz
plan9port-30f6ae144c291409de3657c4bbbaf4983a516772.tar.bz2
plan9port-30f6ae144c291409de3657c4bbbaf4983a516772.zip
man
Diffstat (limited to 'man/man1/pem.1')
-rw-r--r--man/man1/pem.16
1 files changed, 3 insertions, 3 deletions
diff --git a/man/man1/pem.1 b/man/man1/pem.1
index 2002ae11..391cd5cc 100644
--- a/man/man1/pem.1
+++ b/man/man1/pem.1
@@ -1,4 +1,4 @@
-.TH PEM 8
+.TH PEM 1
.SH NAME
pemdecode, pemencode \- encode files in Privacy Enhanced Mail (PEM) format
.SH SYNOPSIS
@@ -20,7 +20,7 @@ Privacy Enhanced Mail program but now commonly used for
other applications, notably TLS.
PEM encodes data in base 64
(see
-.IR encode (2))
+.IR encode (3))
between lines of the form:
.IP
.EX
@@ -33,7 +33,7 @@ where
may be any string describing the encoded data.
The most common use of PEM format on Plan 9 is for encoding
X.509 certificates; see
-.IR rsa (8).
+.IR rsa (1).
.PP
.I Pemdecode
extracts the named