From owner-freebsd-net Fri Jun 12 09:25:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13442 for freebsd-net-outgoing; Fri, 12 Jun 1998 09:25:09 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13216; Fri, 12 Jun 1998 09:24:07 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.8.7/8.8.7) id JAA08686; Fri, 12 Jun 1998 09:23:19 -0700 (PDT) (envelope-from dhw) Date: Fri, 12 Jun 1998 09:23:19 -0700 (PDT) From: David Wolfskill Message-Id: <199806121623.JAA08686@pau-amma.whistle.com> To: freebsd-net@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, yurtesen@ispro.net.tr Subject: Re: telnet Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Date: Fri, 12 Jun 1998 14:36:42 +0300 (EET DST) >From: Evren Yurtesen >I want to restrict telnet access to my domain only... >I mean only people from my domain should be able to >access to my server via telnet. >how may I restrict it in Freebsd? See /usr/ports/security/tcp_wrapper/*. >it was so easy when I was using linux, there was >hosts.deny and hosts.allow files... Yeah, those are files that TCP Wrappers uses. Actually, the port builds tcpwrappers with the -DPROCESS_OPTIONS, so you only need one of those files, and you get a lot more flexiblity. >or do linux has this as an advantage to freebsd? Not that I can tell.... david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message