Red Hat NETWORK 3.6 - CLIENT Configuration Manual page 16

12
Option
Option
--gen-ca
,
-h --help
,
-f --force
,
-p= --password=PASSWORD
,
-d= --dir=BUILD_DIRECTORY
--ca-key=FILENAME
--ca-cert=FILENAME
--cert-expiration=CA_CERT_EXPIRE
--set-country=COUNTRY_CODE
--set-state=STATE_OR_PROVINCE
--set-city=CITY_OR_LOCALITY
--set-org=ORGANIZATION
--set-org-unit=ORGANIZATIONAL_HURT
--set-common-name=HOSTNAME
--set-email=EMAIL
--rpm-packager=PACKAGER
--rpm-vendor=VENDOR
,
-v --verbose
--ca-cert-rpm=CA_CERT_RPM
Description
Description
Generate a Certificate Authority (CA) key pair and
public RPM. This must be issued with any of the
remaining options in this table.
Display the help screen with a list of base options
specific to generating and managing a Certificate
Authority.
Forcibly create a new CA private key and/or public
certificate.
The CA password. You will be prompted for this if
it's missing. Record it in a safe manner.
Required for most commands - The directory where
certificates and RPMs are built. The default is
.
./ssl-build
The CA private key filename. The default is
RHN-ORG-PRIVATE-SSL-KEY
The CA public certificate filename. The default is
RHN-ORG-TRUSTED-SSL-CERT
The expiration date of the public CA certificate. The
default is the number of days until one year prior to
epoch rollover (or 01-18-2038).
The two-letter country code. The default is US.
The state or province of the CA. The default is null.
The city or locality. The default is null.
The company or organization. The default is Example
Corp. Inc.
The organizational unit. The default is section.
Not typically set for the CA. - The common name,
typically host plus domain name.
Not typically set for the CA. - The email address.
Packager of the generated RPM, such as "RHN
Admin (rhn-admin@example.com)."
Vendor of the generated RPM, such as "IS/IT
Example Corp."
Display verbose messaging. Accumulative - added
"v"s result in increasing detail.
Rarely changed - RPM name that houses the CA
certificate (the base filename, not
filename-version-release.noarch.rpm).
Chapter 3. SSL Infrastructure
.
.