<?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 Restrict outgoing telnet but allow incoming telent on same box in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/restrict-outgoing-telnet-but-allow-incoming-telent-on-same-box/m-p/2756282#M90265</link>
    <description>How do I allow users to telnet into one specific server for which they are authorized but prevent them from being able to telnet from that box to other servers ?  Also, will SSH or NIS+ help?&lt;BR /&gt;&lt;BR /&gt;Thanks a lot.</description>
    <pubDate>Tue, 02 Jul 2002 13:00:10 GMT</pubDate>
    <dc:creator>Jason_97</dc:creator>
    <dc:date>2002-07-02T13:00:10Z</dc:date>
    <item>
      <title>Restrict outgoing telnet but allow incoming telent on same box</title>
      <link>https://community.hpe.com/t5/operating-system-linux/restrict-outgoing-telnet-but-allow-incoming-telent-on-same-box/m-p/2756282#M90265</link>
      <description>How do I allow users to telnet into one specific server for which they are authorized but prevent them from being able to telnet from that box to other servers ?  Also, will SSH or NIS+ help?&lt;BR /&gt;&lt;BR /&gt;Thanks a lot.</description>
      <pubDate>Tue, 02 Jul 2002 13:00:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/restrict-outgoing-telnet-but-allow-incoming-telent-on-same-box/m-p/2756282#M90265</guid>
      <dc:creator>Jason_97</dc:creator>
      <dc:date>2002-07-02T13:00:10Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict outgoing telnet but allow incoming telent on same box</title>
      <link>https://community.hpe.com/t5/operating-system-linux/restrict-outgoing-telnet-but-allow-incoming-telent-on-same-box/m-p/2756283#M90266</link>
      <description>Move the telnet binary to somewhere else (to your home directory per say. But if you're trying to do any sort of control, look at chrooting a user's shell and remove the telnet binary from the chroot. See &lt;A href="http://ibiblio.org/pub/Linux/docs/howto/Chroot-BIND-HOWTO" target="_blank"&gt;http://ibiblio.org/pub/Linux/docs/howto/Chroot-BIND-HOWTO&lt;/A&gt; (while this is chrooting bind, it should get you started in the right direction)</description>
      <pubDate>Tue, 02 Jul 2002 14:56:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/restrict-outgoing-telnet-but-allow-incoming-telent-on-same-box/m-p/2756283#M90266</guid>
      <dc:creator>Jonathan Sharp_1</dc:creator>
      <dc:date>2002-07-02T14:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: Restrict outgoing telnet but allow incoming telent on same box</title>
      <link>https://community.hpe.com/t5/operating-system-linux/restrict-outgoing-telnet-but-allow-incoming-telent-on-same-box/m-p/2756284#M90267</link>
      <description>The other option is a network/firewall option, deying anything not bound for the local interfaces with a destination port of 23 (telnet).</description>
      <pubDate>Wed, 03 Jul 2002 00:19:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/restrict-outgoing-telnet-but-allow-incoming-telent-on-same-box/m-p/2756284#M90267</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2002-07-03T00:19:20Z</dc:date>
    </item>
  </channel>
</rss>

