<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic PIX firewall &amp; SSL in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66542#M705853</link>
    <description>&lt;P&gt;I need to enable my PIX (506E) firewall for some SSL traffic on ports 993 and 63149. Do I only use the conduit commands to do so or are there extra steps involved. All help greatly appreciated&lt;/P&gt;&lt;P&gt; TIA&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 06:21:19 GMT</pubDate>
    <dc:creator>parbo</dc:creator>
    <dc:date>2020-02-21T06:21:19Z</dc:date>
    <item>
      <title>PIX firewall &amp; SSL</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66542#M705853</link>
      <description>&lt;P&gt;I need to enable my PIX (506E) firewall for some SSL traffic on ports 993 and 63149. Do I only use the conduit commands to do so or are there extra steps involved. All help greatly appreciated&lt;/P&gt;&lt;P&gt; TIA&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:21:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66542#M705853</guid>
      <dc:creator>parbo</dc:creator>
      <dc:date>2020-02-21T06:21:19Z</dc:date>
    </item>
    <item>
      <title>Re: PIX firewall &amp; SSL</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66543#M705861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you have a server on the inside that you need to allow this traffic through, you need to have the static command for the server as well as the conduit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For further information:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_61/config/mngacl.htm#xtocid2" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_61/config/mngacl.htm#xtocid2&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Nairi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Nov 2002 03:50:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66543#M705861</guid>
      <dc:creator>Nairi Adamian</dc:creator>
      <dc:date>2002-11-06T03:50:49Z</dc:date>
    </item>
    <item>
      <title>Re: PIX firewall &amp; SSL</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66544#M705867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Nairi, this is a working configuration that only needs modification. So we do have the mapping in place but now we need to enable SSL communication.&lt;/P&gt;&lt;P&gt;So what commands do we use, is it only the conduit (syntax?) or also other commands.&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Nov 2002 14:00:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66544#M705867</guid>
      <dc:creator>parbo</dc:creator>
      <dc:date>2002-11-06T14:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: PIX firewall &amp; SSL</title>
      <link>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66545#M705872</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, if you are already using conduits, you just need to add a couple of lines for the new ports. If you are using access-lists you need to modify the access-lists.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;conduit permit tcp host x.x.x.x eq 993 any&lt;/P&gt;&lt;P&gt;conduit permit tcp host x.x.x.x eq 63149 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;where x.x.x.x is the server's public address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following sample configuration includes the syntax for both conduits and access-lists:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/customer/707/28.html" target="_blank"&gt;http://www.cisco.com/warp/customer/707/28.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Nairi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 07 Nov 2002 03:59:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-firewall-ssl/m-p/66545#M705872</guid>
      <dc:creator>Nairi Adamian</dc:creator>
      <dc:date>2002-11-07T03:59:55Z</dc:date>
    </item>
  </channel>
</rss>

