<?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: ftpd question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836058#M581422</link>
    <description>yes, you can block it with /var/adm/inetd.sec&lt;BR /&gt;see man inetd.sec  With this you can block a server for an IP or range of IP's (eg. block ftpd for an IP)&lt;BR /&gt;</description>
    <pubDate>Wed, 30 Oct 2002 14:56:38 GMT</pubDate>
    <dc:creator>Stefan Farrelly</dc:creator>
    <dc:date>2002-10-30T14:56:38Z</dc:date>
    <item>
      <title>ftpd question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836056#M581420</link>
      <description>Hi,&lt;BR /&gt;i need to deny remote ftp acces to a particular user.&lt;BR /&gt;That is the only opertione that user can do is like this&lt;BR /&gt;ftp 127.0.0.1&lt;BR /&gt;&lt;BR /&gt;while &lt;BR /&gt;ftp host_name &lt;BR /&gt;from remote host must be refused.&lt;BR /&gt;&lt;BR /&gt;Is it possible?&lt;BR /&gt;&lt;BR /&gt;Thank you&lt;BR /&gt;Luca&lt;BR /&gt;&lt;BR /&gt;p.s.: An entry in ftpusers deny access also from local host.</description>
      <pubDate>Wed, 30 Oct 2002 14:49:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836056#M581420</guid>
      <dc:creator>Luca Rasconi</dc:creator>
      <dc:date>2002-10-30T14:49:07Z</dc:date>
    </item>
    <item>
      <title>Re: ftpd question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836057#M581421</link>
      <description>You can use the /var/adm/inetd.sec file to specify what ip address can use ftp.&lt;BR /&gt;ftp allow xxx.xxx.*</description>
      <pubDate>Wed, 30 Oct 2002 14:50:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836057#M581421</guid>
      <dc:creator>Ken Hubnik_2</dc:creator>
      <dc:date>2002-10-30T14:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: ftpd question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836058#M581422</link>
      <description>yes, you can block it with /var/adm/inetd.sec&lt;BR /&gt;see man inetd.sec  With this you can block a server for an IP or range of IP's (eg. block ftpd for an IP)&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Oct 2002 14:56:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836058#M581422</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2002-10-30T14:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: ftpd question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836059#M581423</link>
      <description>yes, you can block it with /var/adm/inetd.sec&lt;BR /&gt;see man inetd.sec  With this you can block a service for an IP or range of IP's (eg. block ftpd for an IP)&lt;BR /&gt;</description>
      <pubDate>Wed, 30 Oct 2002 14:57:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836059#M581423</guid>
      <dc:creator>Stefan Farrelly</dc:creator>
      <dc:date>2002-10-30T14:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: ftpd question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836060#M581424</link>
      <description>Sorry, I try to explain better:&lt;BR /&gt;there 3 ftp user (they can make only ftp connections), and I need to deny remote access to one only ftp user.&lt;BR /&gt;The other can do it.&lt;BR /&gt;&lt;BR /&gt;Bye&lt;BR /&gt;Luca</description>
      <pubDate>Wed, 30 Oct 2002 15:01:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836060#M581424</guid>
      <dc:creator>Luca Rasconi</dc:creator>
      <dc:date>2002-10-30T15:01:46Z</dc:date>
    </item>
    <item>
      <title>Re: ftpd question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836061#M581425</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I think you are going to have to replace ftp with wrapper script that verifies the user is allowed to ftp only to 127.0.0.1.&lt;BR /&gt;&lt;BR /&gt;Move /usr/bin/ftp to another location that is not in your users' search path and replace it with your script.&lt;BR /&gt;&lt;BR /&gt;inetd.sec will not work.  It will deny incoming connections only.  Further, it is for IP addresses only, not users.&lt;BR /&gt;&lt;BR /&gt;ftpusers will not work since you want this user to be able to ftp to the local host.  Also, it's only for incoming connections, not outgoing.&lt;BR /&gt;&lt;BR /&gt;Why do you want the user to be able to ftp to the local host?  Seems he could simply use cp.&lt;BR /&gt;&lt;BR /&gt;Darrell</description>
      <pubDate>Wed, 30 Oct 2002 15:11:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836061#M581425</guid>
      <dc:creator>Darrell Allen</dc:creator>
      <dc:date>2002-10-30T15:11:58Z</dc:date>
    </item>
    <item>
      <title>Re: ftpd question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836062#M581426</link>
      <description>Hi Darrel, &lt;BR /&gt;you are right: why it needs this behaviour?&lt;BR /&gt;I simply received this strange (for me) request. I asked him the same question you asked me and I'm waiting for his reponse.&lt;BR /&gt;&lt;BR /&gt;Thank you all&lt;BR /&gt;Luca</description>
      <pubDate>Wed, 30 Oct 2002 15:13:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftpd-question/m-p/2836062#M581426</guid>
      <dc:creator>Luca Rasconi</dc:creator>
      <dc:date>2002-10-30T15:13:48Z</dc:date>
    </item>
  </channel>
</rss>

