Registering With Activation Keys - Red Hat NETWORK 4.1.0 Reference Manual

Chapter 2. Red Hat Update Agent
9. noBootLoader
10. serverURL
11. fileSkipList
12. sslCACert
13. noReplaceConfig
14. useNoSSLForPackage No
15. systemIdPath
16. enableProxyAuth
17. retrieveSource
18. versionOverride
19. headerFetchCount
20. networkRetries
21. enableProxy
22. proxyPassword
23. noSSLServerURL
24. keepAfterInstall
25. proxyUser
26. removeSkipList
27. useGPG
28. gpgKeyRing
29. httpProxy
30. headerCacheSize
31. forceInstall
Enter number of item to edit < return to exit, q to quit without saving > :
Enter the number of the item to modify and enter a new value for the option. When you
finish changing your configuration, press [Enter] to save your changes and exit. Press [q]
and then [Enter] to quit without saving your changes.
Important
Although this is not configurable, users should still make note that the port used by the
Red Hat Update Agent is 443 for SSL (HTTPS) and 80 for non-SSL (HTTP). By de-
fault,
up2date
allow connections over port 443. To bypass SSL, change the protocol for serverURL from
https to http in the

2.5. Registering with Activation Keys

In addition to the standard Red Hat Update Agent interface,
aimed at batch processing system registrations: activation keys. Each unique key can be
used to register Red Hat Enterprise Linux systems, entitle them to an RHN service level,
No
https://xmlrpc.rhn.redhat.com/XMLRPC
[]
/usr/share/rhn/RHNS-CA-CERT
Yes
/etc/sysconfig/rhn/systemid
No
No
10
5
No
http://xmlrpc.rhn.redhat.com/XMLRPC
No
['kernel*']
Yes
/etc/sysconfig/rhn/up2date-keyring.gpg
40
No
uses SSL only. For this reason, users should ensure that their firewalls
/etc/sysconfig/rhn/up2date
configuration file.
offers a utility
up2date
39