This public directory can be inspected easily by simply browsing to it via any web browser: http://proxy-
or-sat.example.com/pub/.
The CA SSL public certificate in that directory can be downloaded to a client system using wget or
curl. For example:
curl -O http://proxy-or-sat.exam ple.com/pub/RHN-ORG-TRUSTED-SSL-CERT
wget http://proxy-or-sat.example.com/pub/RHN-ORG-TRUSTED-SSL-CERT
Alternatively, if the CA SSL public certificate RPM resides in the /pub directory, it can be installed on a
client system directly:
rpm -Uvh \
http://proxy-or-sat.example.com/pub/rhn-org-trusted-ssl-cert-VER-REL.noarch.rpm
Confirm the actual name of the certificate or RPM before running these commands.
3.4. Configuring Client Systems
Once the RPM or raw certificate has been deployed to a client system, the administrator of that system
must then alter the configuration files of the Red Hat Update Agent and the Red Hat Network
Registration Client (if necessary) to use the new CA SSL public certificate file and connect to the
appropriate RHN Proxy Server or RHN Satellite Server. T he generally accepted location for that CA SSL
public certificate is in the /usr/share/rhn directory.
The RHN Proxy Server and RHN Satellite Server both have RHN Boot strap installed by default, which
can greatly reduce these repetitive steps and simplify the process of registering and configuring client
systems. Please refer Chapter 5, Using RHN Bootstrap for details.
Comentarios a estos manuales