It was found that when RHN Proxy was used as a proxy to connect to RHN Satellite, certain pages that should have been protected via SSL (in direct to Satellite connections) were in fact only protected between RHN Proxy and RHN Satellite; the connection between the client and RHN Proxy was not protected via SSL. This could leak confidential information or authentication credentials when accessing RHN Satellite via RHN Proxy. By default, yum clients and rhn_register will always communicate with RHN Proxy over HTTPS.
(In reply to comment #0) > It was found that when RHN Proxy was used as a proxy to connect to RHN > Satellite, certain pages that should have been protected via SSL (in direct Could you please list these "certain pages"?
(In reply to comment #3) > (In reply to comment #0) > > It was found that when RHN Proxy was used as a proxy to connect to RHN > > Satellite, certain pages that should have been protected via SSL (in direct > > Could you please list these "certain pages"? - "/Login.do" - "/ReLogin.do"
Statement: This issue was corrected in RHN Satellite 5.6; earlier versions of RHN Satellite are affected. As RHN Satellite is now in the Production 2 phase of its support and maintenance life cycle, there are currently no plans to address this in future updates for RHN Satellite 5.5 and earlier. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/site/support/policy/updates/satellite.
This was addressed in the Satellite-Proxy 5.6.0 release available at: https://rhn.redhat.com/errata/RHEA-2013-1392.html