<?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: telnet security in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006696#M425693</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If you are unable to use ACLs, you could create a telnet wrapper script.&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;TELNET=/obfuscated/path/to/telnet&lt;BR /&gt;DENIED_USER=user1&lt;BR /&gt;[[ "$(whoami)" = "${DENIED_USER}" ]] &amp;amp;&amp;amp; echo "telnet denied" || ${TELNET}&lt;BR /&gt;exit&lt;BR /&gt;&lt;BR /&gt;Move the telnet binary to an obscure directory that's not listed in ${PATH}.  Save the script as /usr/bin/telnet.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
    <pubDate>Wed, 04 Oct 2006 07:14:56 GMT</pubDate>
    <dc:creator>spex</dc:creator>
    <dc:date>2006-10-04T07:14:56Z</dc:date>
    <item>
      <title>telnet security</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006694#M425691</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;  for security reason,how can I deny a certain user telnet from a host to all other hosts?modify only can do in this host,any idea?</description>
      <pubDate>Wed, 04 Oct 2006 04:06:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006694#M425691</guid>
      <dc:creator>Ming.Dynasty</dc:creator>
      <dc:date>2006-10-04T04:06:40Z</dc:date>
    </item>
    <item>
      <title>Re: telnet security</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006695#M425692</link>
      <description>Hi,&lt;BR /&gt;the only way I know of and I have never used it in a real environment, is to create an ACL for the telnet command:&lt;BR /&gt;&lt;BR /&gt;setacl -m user:fred:--- /usr/bin/telnet&lt;BR /&gt;&lt;BR /&gt;This will give the user fred a message of "Permissions denied" when he issues the telnet command.</description>
      <pubDate>Wed, 04 Oct 2006 04:30:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006695#M425692</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2006-10-04T04:30:10Z</dc:date>
    </item>
    <item>
      <title>Re: telnet security</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006696#M425693</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;If you are unable to use ACLs, you could create a telnet wrapper script.&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/sh&lt;BR /&gt;TELNET=/obfuscated/path/to/telnet&lt;BR /&gt;DENIED_USER=user1&lt;BR /&gt;[[ "$(whoami)" = "${DENIED_USER}" ]] &amp;amp;&amp;amp; echo "telnet denied" || ${TELNET}&lt;BR /&gt;exit&lt;BR /&gt;&lt;BR /&gt;Move the telnet binary to an obscure directory that's not listed in ${PATH}.  Save the script as /usr/bin/telnet.&lt;BR /&gt;&lt;BR /&gt;PCS</description>
      <pubDate>Wed, 04 Oct 2006 07:14:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006696#M425693</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-10-04T07:14:56Z</dc:date>
    </item>
    <item>
      <title>Re: telnet security</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006697#M425694</link>
      <description>Thanks for reply&lt;BR /&gt;&lt;BR /&gt;but if the user ftp in a new telnet program,all modify will not work. anyway it works for rookies well. lol</description>
      <pubDate>Wed, 04 Oct 2006 21:31:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006697#M425694</guid>
      <dc:creator>Ming.Dynasty</dc:creator>
      <dc:date>2006-10-04T21:31:09Z</dc:date>
    </item>
    <item>
      <title>Re: telnet security</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006698#M425695</link>
      <description>I don't think that limiting access to the client will be enough, since the user can easily install their own client, or compile their own locally.&lt;BR /&gt;&lt;BR /&gt;I think you're only option is to use something like a restricted-shell for that user with a very carefully-crafted white-list of commands. &lt;BR /&gt;&lt;BR /&gt;That said... I think your requirement may be going about it the wrong way.  In general, the best security solutions rely on the resource to protect itself (in your case the hosts that you don't want the user to access).  Going the other way around is asking for trouble... as one simple example illuminates... &lt;BR /&gt;&lt;BR /&gt;Say you do a bunch of work to restrict telnet... the user plugs a laptop into a port on your network... and accesses the servers... &lt;BR /&gt;&lt;BR /&gt;I'd think carefully about the threat you're trying to protect against, before investing in what could turn out to be a brittle solution.&lt;BR /&gt;&lt;BR /&gt;Hope that helps,&lt;BR /&gt;-Robert</description>
      <pubDate>Thu, 05 Oct 2006 10:42:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006698#M425695</guid>
      <dc:creator>Robert Fritz</dc:creator>
      <dc:date>2006-10-05T10:42:33Z</dc:date>
    </item>
    <item>
      <title>Re: telnet security</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006699#M425696</link>
      <description>Sorted out&lt;BR /&gt;&lt;BR /&gt;thanks all</description>
      <pubDate>Thu, 05 Oct 2006 20:22:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/telnet-security/m-p/5006699#M425696</guid>
      <dc:creator>Ming.Dynasty</dc:creator>
      <dc:date>2006-10-05T20:22:48Z</dc:date>
    </item>
  </channel>
</rss>

