<?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: ftponly user in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503619#M653841</link>
    <description>Hello himacs!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I have created a user only for ftp access ,no shell access.Its worked fine&lt;BR /&gt;&lt;BR /&gt;Actually, ftp only account is a misnomer. All it reduces to is a user account on the system with /usr/bin/false as shell or similar, to avoid successful login of this user using login, r*, ...&lt;BR /&gt;&lt;BR /&gt;&amp;gt; is there any chance password locking&lt;BR /&gt;&lt;BR /&gt;Yes, actually if you have enforced a max number of authentication tries (man 4 security - AUTH_MAXTRIES) ssh login failures are counted too (man 5 pam_hpsec).&lt;BR /&gt;&lt;BR /&gt;&amp;gt; /usr/bin/false: No such file or directory&lt;BR /&gt;&lt;BR /&gt;As pointed out, an ftp only user is still a valid user account but with /usr/bin/false as login shell, which will prevent access.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;You can avoid ssh failed authentication attempts from being counted by denying access to specific users.&lt;BR /&gt;&lt;BR /&gt;As already suggested by Steven Schweda, this can be done in the sshd_config file:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1373872" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1373872&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Kobylka</description>
    <pubDate>Sat, 26 Sep 2009 07:38:59 GMT</pubDate>
    <dc:creator>kobylka</dc:creator>
    <dc:date>2009-09-26T07:38:59Z</dc:date>
    <item>
      <title>ftponly user</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503615#M653837</link>
      <description>Hi Admins,&lt;BR /&gt;&lt;BR /&gt;I have created a user only for ftp access ,no shell access.Its worked fine.&lt;BR /&gt;But when i trying to ssh got below message.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt;ssh pavan@UAEDXBPDCAPPP01&lt;BR /&gt;The authenticity of host 'uaedxbpdcappp01 (10.11.10.15)' can't be established.&lt;BR /&gt;RSA key fingerprint is d5:26:c4:f0:7e:7c:e4:dc:da:bd:7e:64:a0:6b:26:39.&lt;BR /&gt;Are you sure you want to continue connecting (yes/no)? yes&lt;BR /&gt;Warning: Permanently added 'uaedxbpdcappp01' (RSA) to the list of known hosts.&lt;BR /&gt;Password:&lt;BR /&gt;Password:&lt;BR /&gt;Last login: Sat Sep 26 00:42:29 2009 from UAEDXBPDCAPPP01&lt;BR /&gt;/usr/bin/false: No such file or directory&lt;BR /&gt;Connection to UAEDXBPDCAPPP01 closed.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;why this showing &lt;BR /&gt;Please suggest&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;himacs&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Sep 2009 19:55:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503615#M653837</guid>
      <dc:creator>himacs</dc:creator>
      <dc:date>2009-09-25T19:55:23Z</dc:date>
    </item>
    <item>
      <title>Re: ftponly user</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503616#M653838</link>
      <description>&lt;!--!*#--&gt;&amp;gt; I have created a user only for ftp access&lt;BR /&gt;&amp;gt; ,no shell access.  [...]&lt;BR /&gt;&lt;BR /&gt;So why would you expect SSH to work using&lt;BR /&gt;an FTP-only account?  What do you think that&lt;BR /&gt;"only" means?&lt;BR /&gt;&lt;BR /&gt;"SSH" = "Secure SHell".&lt;BR /&gt;&lt;BR /&gt;   "no shell access"&lt;BR /&gt;   "ssh"&lt;BR /&gt;&lt;BR /&gt;Think about it.</description>
      <pubDate>Fri, 25 Sep 2009 21:03:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503616#M653838</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-09-25T21:03:32Z</dc:date>
    </item>
    <item>
      <title>Re: ftponly user</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503617#M653839</link>
      <description>&lt;BR /&gt;Hi Steven,&lt;BR /&gt;&lt;BR /&gt;Actually my concern is abt password.If anybody tries the ssh with the same user,is there any chance password locking ,since its not accept password.&lt;BR /&gt;&lt;BR /&gt;And why this showing &lt;BR /&gt;Please advice..&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;himacs</description>
      <pubDate>Fri, 25 Sep 2009 23:50:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503617#M653839</guid>
      <dc:creator>himacs</dc:creator>
      <dc:date>2009-09-25T23:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: ftponly user</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503618#M653840</link>
      <description>&lt;!--!*#--&gt;&amp;gt; [...] is there any chance password locking&lt;BR /&gt;&amp;gt; [...]&lt;BR /&gt;&lt;BR /&gt;Good question.  It might be best to disable&lt;BR /&gt;SSH access (or, at least password&lt;BR /&gt;authentication) for this user.  I know&lt;BR /&gt;nothing, but I'd guess that this could be&lt;BR /&gt;done in the server's SSH config files.  It&lt;BR /&gt;might also be possible in the user's SSH&lt;BR /&gt;client config files, but the user might be&lt;BR /&gt;able to FTP in a change to those.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; [...] /usr/bin/false: No such file or&lt;BR /&gt;&amp;gt; directory [...]&lt;BR /&gt;&lt;BR /&gt;I don't know that, either, but it may be&lt;BR /&gt;simply a poor message.  It sure can't use&lt;BR /&gt;that shell the way it can use a normal shell,&lt;BR /&gt;so I'd guess that it gets a failure of some&lt;BR /&gt;kind when it tries.</description>
      <pubDate>Sat, 26 Sep 2009 02:53:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503618#M653840</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-09-26T02:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: ftponly user</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503619#M653841</link>
      <description>Hello himacs!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; I have created a user only for ftp access ,no shell access.Its worked fine&lt;BR /&gt;&lt;BR /&gt;Actually, ftp only account is a misnomer. All it reduces to is a user account on the system with /usr/bin/false as shell or similar, to avoid successful login of this user using login, r*, ...&lt;BR /&gt;&lt;BR /&gt;&amp;gt; is there any chance password locking&lt;BR /&gt;&lt;BR /&gt;Yes, actually if you have enforced a max number of authentication tries (man 4 security - AUTH_MAXTRIES) ssh login failures are counted too (man 5 pam_hpsec).&lt;BR /&gt;&lt;BR /&gt;&amp;gt; /usr/bin/false: No such file or directory&lt;BR /&gt;&lt;BR /&gt;As pointed out, an ftp only user is still a valid user account but with /usr/bin/false as login shell, which will prevent access.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;You can avoid ssh failed authentication attempts from being counted by denying access to specific users.&lt;BR /&gt;&lt;BR /&gt;As already suggested by Steven Schweda, this can be done in the sshd_config file:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1373872" target="_blank"&gt;http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1373872&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Kobylka</description>
      <pubDate>Sat, 26 Sep 2009 07:38:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftponly-user/m-p/4503619#M653841</guid>
      <dc:creator>kobylka</dc:creator>
      <dc:date>2009-09-26T07:38:59Z</dc:date>
    </item>
  </channel>
</rss>

