 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: RHEL 4 installer bug: HTTPS not exempted despite best efforts</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/enterprise-linux/rhel-4-installer-bug-https-not-exempted-despite-best-efforts/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/enterprise-linux/rhel-4-installer-bug-https-not-exempted-despite-best-efforts/</link>
	<description>A SearchEnterpriseLinux.com blog</description>
	<lastBuildDate>Wed, 28 Nov 2012 02:36:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Schley Andrew Kutz</title>
		<link>http://itknowledgeexchange.techtarget.com/enterprise-linux/rhel-4-installer-bug-https-not-exempted-despite-best-efforts/#comment-1301</link>
		<dc:creator>Schley Andrew Kutz</dc:creator>
		<pubDate>Mon, 04 Feb 2008 20:03:16 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/enterprise-linux/rhel-4-installer-bug-https-not-exempted-despite-best-efforts/#comment-1301</guid>
		<description><![CDATA[Yes, no kidding. I am sorry if I seem frustrated, but this is the exact same response I got from Red Hat that I had to beat them over the head with. I know what ports need to be open. My point is that the RHEL 4 installer SAYS it will open specific ports and fails to do so. Satellite was the impetus for finding the problem, whereas the problem is the fact that the RHEL 4 installer has a bug in it.

Make sense?]]></description>
		<content:encoded><![CDATA[<p>Yes, no kidding. I am sorry if I seem frustrated, but this is the exact same response I got from Red Hat that I had to beat them over the head with. I know what ports need to be open. My point is that the RHEL 4 installer SAYS it will open specific ports and fails to do so. Satellite was the impetus for finding the problem, whereas the problem is the fact that the RHEL 4 installer has a bug in it.</p>
<p>Make sense?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pablo</title>
		<link>http://itknowledgeexchange.techtarget.com/enterprise-linux/rhel-4-installer-bug-https-not-exempted-despite-best-efforts/#comment-1300</link>
		<dc:creator>Pablo</dc:creator>
		<pubDate>Mon, 04 Feb 2008 18:58:51 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/enterprise-linux/rhel-4-installer-bug-https-not-exempted-despite-best-efforts/#comment-1300</guid>
		<description><![CDATA[Hi, on

http://www.redhat.com/docs/manuals/satellite/Red_Hat_Network_Satellite-5.0.0/html/Installation_Guide/s1-requirements-additional.html

It&#039;s crearly stated which ports you need to open in order to work with it..

Regards
Pablo]]></description>
		<content:encoded><![CDATA[<p>Hi, on</p>
<p><a href="http://www.redhat.com/docs/manuals/satellite/Red_Hat_Network_Satellite-5.0.0/html/Installation_Guide/s1-requirements-additional.html" rel="nofollow">http://www.redhat.com/docs/manuals/satellite/Red_Hat_Network_Satellite-5.0.0/html/Installation_Guide/s1-requirements-additional.html</a></p>
<p>It&#8217;s crearly stated which ports you need to open in order to work with it..</p>
<p>Regards<br />
Pablo</p>
]]></content:encoded>
	</item>
</channel>
</rss>
