<?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: FTP Security issue in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474819#M760064</link>
    <description>Kong,&lt;BR /&gt;Frankly speaking FTP is a very nice service, but it is very dangerous too !!!. So my advice to you will be:  &lt;BR /&gt;    Allow the guys to do telnet "in"to your system and then ask them to ftp "out" to their requisite place. It will be better if you can disable ftp service.&lt;BR /&gt;    &lt;BR /&gt;   But if you really want to continue with  ftp, I would like to suggest something. First you create an account with /bin/false as its shell. Give that account rights to only a particula area on your system. Keep the account password protected (increased security). Disable ftp access for everybody else, by adding their names to /etc/ftpusers file. Keep only one entry in /etc/shells file as &lt;BR /&gt;/bin/false (increased security).&lt;BR /&gt;   Hope this helps....&lt;BR /&gt;Suhas :-)....</description>
    <pubDate>Mon, 18 Dec 2000 15:14:50 GMT</pubDate>
    <dc:creator>Suhas_2</dc:creator>
    <dc:date>2000-12-18T15:14:50Z</dc:date>
    <item>
      <title>FTP Security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474816#M760061</link>
      <description>Our system (HP-UX 10.20 &amp;amp; 11.00) allows our users to FTP &amp;amp; TELNET from their home to access the resources.&lt;BR /&gt;&lt;BR /&gt;However, I was told by a friend that allowing FTP is a big security lax - that via FTP, users can actually flood the system with messages &amp;amp; get to the root a/c.&lt;BR /&gt;&lt;BR /&gt;Would like to check how this is done &amp;amp; how to prevent it.&lt;BR /&gt;</description>
      <pubDate>Mon, 18 Dec 2000 04:17:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474816#M760061</guid>
      <dc:creator>Kong Kian Chay</dc:creator>
      <dc:date>2000-12-18T04:17:08Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474817#M760062</link>
      <description>Kong:&lt;BR /&gt;If you are allowing your users out-going ftp access, then there is nothing much to worry about; however, if you are allowing them ftp access into your network/server, you have to take some precautions.&lt;BR /&gt;&lt;BR /&gt;Allowing unrestricted access to any service on your server is a potential security risk.  I would recommend that if you do not already have one-&lt;BR /&gt;&lt;BR /&gt;1. set up your servers behind a firewall&lt;BR /&gt;2.  consider using some form of VPN technology to allow your users to connect from home&lt;BR /&gt;3.  get the latest security patches for all services that you are offering (and keep a close eye on bug reports as they come out)&lt;BR /&gt;4.  Visit the excellent security related site: &lt;A href="http://www.securityfocus.com" target="_blank"&gt;http://www.securityfocus.com&lt;/A&gt; and &lt;A href="http://www.sans.org" target="_blank"&gt;http://www.sans.org&lt;/A&gt;&lt;BR /&gt;for more information on exploits.&lt;BR /&gt;&lt;BR /&gt;To answer your questions more specifically, there are vulnerable versions of ftp out there that can give a user root access/root shell via a buffer overflow.  These kinds of attacks are generally prevented by getting the latest versions of your ftp daemon.  &lt;BR /&gt;&lt;BR /&gt;good luck</description>
      <pubDate>Mon, 18 Dec 2000 04:37:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474817#M760062</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-12-18T04:37:31Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474818#M760063</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Kofi is right ! ftp could be a major security issue if you leave it unrestricted.&lt;BR /&gt;&lt;BR /&gt;Make sure that you have applied the latest ftp patch (PHNE_21936 for 11.0, PHNE_22057&lt;BR /&gt; for 10.20)&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Dan</description>
      <pubDate>Mon, 18 Dec 2000 09:47:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474818#M760063</guid>
      <dc:creator>Dan Hetzel</dc:creator>
      <dc:date>2000-12-18T09:47:49Z</dc:date>
    </item>
    <item>
      <title>Re: FTP Security issue</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474819#M760064</link>
      <description>Kong,&lt;BR /&gt;Frankly speaking FTP is a very nice service, but it is very dangerous too !!!. So my advice to you will be:  &lt;BR /&gt;    Allow the guys to do telnet "in"to your system and then ask them to ftp "out" to their requisite place. It will be better if you can disable ftp service.&lt;BR /&gt;    &lt;BR /&gt;   But if you really want to continue with  ftp, I would like to suggest something. First you create an account with /bin/false as its shell. Give that account rights to only a particula area on your system. Keep the account password protected (increased security). Disable ftp access for everybody else, by adding their names to /etc/ftpusers file. Keep only one entry in /etc/shells file as &lt;BR /&gt;/bin/false (increased security).&lt;BR /&gt;   Hope this helps....&lt;BR /&gt;Suhas :-)....</description>
      <pubDate>Mon, 18 Dec 2000 15:14:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftp-security-issue/m-p/2474819#M760064</guid>
      <dc:creator>Suhas_2</dc:creator>
      <dc:date>2000-12-18T15:14:50Z</dc:date>
    </item>
  </channel>
</rss>

