I've encountered a couple of problems when trying to use rhn-ssl-tool to package keys and certificates for use with jabberd.
- It appears that server.pem is not truncated when opened for writing by rhn-ssl-tool; some of the previous contents can be found at the end of the file.
- Only the Satellite's certificate and keypair are written to server.pem. I believe that this file needs to contain the entire certificate chain up to the root CA for XMPP clients to be able to verify the Satellite's certificate.
Steps to Reproduce:
sudo rhn-ssl-tool --gen-server --dir=/root/ssl-build --key-only
sudo rhn-ssl-tool --gen-server --dir=/root/ssl-build --cert-req-only --set-country ... --set-state ... --set-city ... --set-org ... --set-org-unit ... --set-email ...
Acquire a signed cert and placed it in /root/ssl-build/`hostname --short`/server.csr
sudo rhn-ssl-tool --gen-server --dir=/root/ssl-build --rpm-only
sudo rpm -Uhv /root/ssl-build/.../rhn-org-httpd-ssl-key-pair-...-1.0-5.noarch.rpm
sudo service jabberd start && sudo service osa-dispatcher start
Initializing jabberd processes ...
Starting router: [ OK ]
Starting sm: [ OK ]
Starting c2s: [ OK ]
Starting s2s: [ OK ]
Starting osa-dispatcher: Spacewalk 14195 2014/08/13 17:32:06 +01:00: ('Traceback caught:',)
Spacewalk 14195 2014/08/13 17:32:06 +01:00: ('Traceback (most recent call last):\n File "/usr/share/rhn/osad/jabber_lib.py", line 616, in connect\n ssl.do_handshake()\nError: [(\'SSL routines\', \'SSL3_GET_SERVER_CERTIFICATE\', \'certificate verify failed\')]\n',)
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.
This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED.
Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.