Fix tyops pointed out by Igor Sobrado in PR misc/19627

openssl_rand(1)     - generater (generator?)
openssl_req(1)      - stateOrPrivinceName (stateOrProvinceName),
			eg. (e.g., Latin exempli gratia)
openssl_rsa(1)      - thse (these, perhaps those)
openssl_s_client(1) - implicitely (implicitly),
			renegociated (renegotiated)
openssl_x509(1)     - beginnging (beginning, whow!),
			repesents (represents)
This commit is contained in:
jschauma 2003-01-01 21:43:13 +00:00
parent b49ef594e9
commit ba40d7ee64
5 changed files with 15 additions and 15 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: openssl_rand.1,v 1.8 2002/08/09 16:15:46 itojun Exp $
.\" $NetBSD: openssl_rand.1,v 1.9 2003/01/01 21:43:13 jschauma Exp $
.\"
.\" Automatically generated by Pod::Man version 1.02
.\" Sat Aug 10 00:55:24 2002
@ -156,7 +156,7 @@ libcrypto, -lcrypto
.SH "DESCRIPTION"
.IX Header "DESCRIPTION"
The \fBrand\fR command outputs \fInum\fR pseudo-random bytes after seeding
the random number generater once. As in other \fBopenssl\fR command
the random number generator once. As in other \fBopenssl\fR command
line tools, \s-1PRNG\s0 seeding uses the file \fI$HOME/\fR\fB.rnd\fR or \fB.rnd\fR
in addition to the files given in the \fB\-rand\fR option. A new
\&\fI$HOME\fR/\fB.rnd\fR or \fB.rnd\fR file will be written back if enough

View File

@ -1,4 +1,4 @@
.\" $NetBSD: openssl_req.1,v 1.8 2002/08/09 16:15:46 itojun Exp $
.\" $NetBSD: openssl_req.1,v 1.9 2003/01/01 21:43:13 jschauma Exp $
.\"
.\" Automatically generated by Pod::Man version 1.02
.\" Sat Aug 10 00:55:25 2002
@ -445,7 +445,7 @@ be input by calling it \*(L"1.organizationName\*(R".
The actual permitted field names are any object identifier short or
long names. These are compiled into OpenSSL and include the usual
values such as commonName, countryName, localityName, organizationName,
organizationUnitName, stateOrPrivinceName. Additionally emailAddress
organizationUnitName, stateOrProvinceName. Additionally emailAddress
is include as well as name, surname, givenName initials and dnQualifier.
.PP
Additional object identifiers can be defined with the \fBoid_file\fR or
@ -508,13 +508,13 @@ Sample configuration file prompting for field values:
\& countryName_max = 2
.Ve
.Vb 1
\& localityName = Locality Name (eg, city)
\& localityName = Locality Name (e.g. city)
.Ve
.Vb 1
\& organizationalUnitName = Organizational Unit Name (eg, section)
\& organizationalUnitName = Organizational Unit Name (e.g. section)
.Ve
.Vb 2
\& commonName = Common Name (eg, YOUR name)
\& commonName = Common Name (e.g. YOUR name)
\& commonName_max = 64
.Ve
.Vb 2

View File

@ -1,4 +1,4 @@
.\" $NetBSD: openssl_rsa.1,v 1.8 2002/08/09 16:15:46 itojun Exp $
.\" $NetBSD: openssl_rsa.1,v 1.9 2003/01/01 21:43:13 jschauma Exp $
.\"
.\" Automatically generated by Pod::Man version 1.02
.\" Sat Aug 10 00:55:27 2002
@ -259,7 +259,7 @@ and Microsoft \s-1IIS\s0 .key files, this uses unsalted \s-1RC4\s0 for its encry
It is not very secure and so should only be used when necessary.
.PP
Some newer version of \s-1IIS\s0 have additional data in the exported .key
files. To use thse with the utility view the file with a binary editor
files. To use these with the utility view the file with a binary editor
and look for the string \*(L"private-key\*(R", then trace back to the byte
sequence 0x30, 0x82 (this is an \s-1ASN1\s0 \s-1SEQUENCE\s0). Copy all the data
from this point onwards to another file and use that as the input

View File

@ -1,4 +1,4 @@
.\" $NetBSD: openssl_s_client.1,v 1.9 2002/08/09 16:15:46 itojun Exp $
.\" $NetBSD: openssl_s_client.1,v 1.10 2003/01/01 21:43:13 jschauma Exp $
.\"
.\" Automatically generated by Pod::Man version 1.02
.\" Sat Aug 10 00:55:28 2002
@ -252,7 +252,7 @@ inhibit shutting down the connection when end of file is reached in the
input.
.Ip "\fB\-quiet\fR" 4
.IX Item "-quiet"
inhibit printing of session and certificate information. This implicitely
inhibit printing of session and certificate information. This implicitly
turns on \fB\-ign_eof\fR as well.
.Ip "\fB\-ssl2\fR, \fB\-ssl3\fR, \fB\-tls1\fR, \fB\-no_ssl2\fR, \fB\-no_ssl3\fR, \fB\-no_tls1\fR" 4
.IX Item "-ssl2, -ssl3, -tls1, -no_ssl2, -no_ssl3, -no_tls1"
@ -286,7 +286,7 @@ all others.
If a connection is established with an \s-1SSL\s0 server then any data received
from the server is displayed and any key presses will be sent to the
server. When used interactively (which means neither \fB\-quiet\fR nor \fB\-ign_eof\fR
have been given), the session will be renegociated if the line begins with an
have been given), the session will be renegotiated if the line begins with an
\&\fBR\fR, and if the line begins with a \fBQ\fR or if end of file is reached, the
connection will be closed down.
.SH "NOTES"

View File

@ -1,4 +1,4 @@
.\" $NetBSD: openssl_x509.1,v 1.9 2002/08/09 16:15:47 itojun Exp $
.\" $NetBSD: openssl_x509.1,v 1.10 2003/01/01 21:43:14 jschauma Exp $
.\"
.\" Automatically generated by Pod::Man version 1.02
.\" Sat Aug 10 00:55:36 2002
@ -448,7 +448,7 @@ a multiline format. It is equivalent \fBesc_ctrl\fR, \fBesc_msb\fR, \fBsep_multi
.Ip "\fBesc_2253\fR" 4
.IX Item "esc_2253"
escape the \*(L"special\*(R" characters required by \s-1RFC2253\s0 in a field That is
\&\fB,+"<>;\fR. Additionally \fB#\fR is escaped at the beginnging of a string
\&\fB,+"<>;\fR. Additionally \fB#\fR is escaped at the beginning of a string
and a space character at the beginning or end of a string.
.Ip "\fBesc_ctrl\fR" 4
.IX Item "esc_ctrl"
@ -494,7 +494,7 @@ content octets will be displayed. Both options use the \s-1RFC2253\s0
.IX Item "dump_nostr"
dump non character string types (for example \s-1OCTET\s0 \s-1STRING\s0) if this
option is not set then non character string types will be displayed
as though each content octet repesents a single character.
as though each content octet represents a single character.
.Ip "\fBdump_all\fR" 4
.IX Item "dump_all"
dump all fields. This option when used with \fBdump_der\fR allows the