<?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 Re: PIX Authenticaion for outbound SSH &amp; FTP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-authenticaion-for-outbound-ssh-ftp/m-p/125079#M606369</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can define what traffic should be authenticated through the PIX with the command you've shown, but users can only still authenticate using Telnet, FTP or HTTP traffic.  There's nothing in the SSH protocol for example, that can have the PIX intercept it and display a username/password request to the user.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a read through &lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/atp52.html" target="_blank"&gt;http://www.cisco.com/warp/public/110/atp52.html&lt;/A&gt; and see how you get on.  Pay particular attention to the debug/syslog messages, they'll help you out a lot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 05 May 2003 04:04:17 GMT</pubDate>
    <dc:creator>gfullage</dc:creator>
    <dc:date>2003-05-05T04:04:17Z</dc:date>
    <item>
      <title>PIX Authenticaion for outbound SSH &amp; FTP</title>
      <link>https://community.cisco.com/t5/network-security/pix-authenticaion-for-outbound-ssh-ftp/m-p/125078#M606367</link>
      <description>&lt;P&gt;I have a PIX firewall in which I wish to authenticate outbound connections for slected users of SSH &amp;amp; FTP against an internal AAA server, using TACACS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this functionality supported ?&lt;/P&gt;&lt;P&gt;I have created an access list to match the traffic SSH-Tracker .&lt;/P&gt;&lt;P&gt;I have related the access list to the authenticate, aaa authentication match SSH-Tracker inside tacserv.&lt;/P&gt;&lt;P&gt;I have glodal nats in place.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I suspect I am missing something of the functionality is not there yet ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help appriciated.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:43:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-authenticaion-for-outbound-ssh-ftp/m-p/125078#M606367</guid>
      <dc:creator>dofaulkner</dc:creator>
      <dc:date>2020-02-21T06:43:22Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Authenticaion for outbound SSH &amp; FTP</title>
      <link>https://community.cisco.com/t5/network-security/pix-authenticaion-for-outbound-ssh-ftp/m-p/125079#M606369</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can define what traffic should be authenticated through the PIX with the command you've shown, but users can only still authenticate using Telnet, FTP or HTTP traffic.  There's nothing in the SSH protocol for example, that can have the PIX intercept it and display a username/password request to the user.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a read through &lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/110/atp52.html" target="_blank"&gt;http://www.cisco.com/warp/public/110/atp52.html&lt;/A&gt; and see how you get on.  Pay particular attention to the debug/syslog messages, they'll help you out a lot.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 May 2003 04:04:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-authenticaion-for-outbound-ssh-ftp/m-p/125079#M606369</guid>
      <dc:creator>gfullage</dc:creator>
      <dc:date>2003-05-05T04:04:17Z</dc:date>
    </item>
    <item>
      <title>Re: PIX Authenticaion for outbound SSH &amp; FTP</title>
      <link>https://community.cisco.com/t5/network-security/pix-authenticaion-for-outbound-ssh-ftp/m-p/125080#M606370</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Doug,&lt;/P&gt;&lt;P&gt;ftp can be authenticated, but ssh not. But you can do it another way. Authenticate the traffic via ftp, http or telnet (https in V6.3 is supported to) and authorize ssh against you tacacs server. Authorization only takes place, when the user is authenticated first. So you can say who is allowed to ftp or ssh or whatever you want.&lt;/P&gt;&lt;P&gt;Hope this helps a bit&lt;/P&gt;&lt;P&gt;Norbert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 05 May 2003 13:44:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-authenticaion-for-outbound-ssh-ftp/m-p/125080#M606370</guid>
      <dc:creator>nsteup</dc:creator>
      <dc:date>2003-05-05T13:44:53Z</dc:date>
    </item>
  </channel>
</rss>

