Date: Thu, 1 Jul 1999 19:42:11 +0200 From: "Roger Rabbit" <ros@intrafish.no> To: "David Pick" <D.M.Pick@qmw.ac.uk> Cc: <freebsd-security@freebsd.org> Subject: SV: tcp wrappers Message-ID: <00c801bec3e9$0cbd9560$2790ccc3@intrafish.no> References: <E10zkhZ-0006Qf-00@xi.css.qmw.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Thnx a lot for the help guys. I got my hands on the tcpserver source and compiled it (I only had the precompiled package and it was a.out) ... works like a dream so tcp wrappers are of no interest anymore. :) -Roger ----- Original Message ----- From: David Pick <D.M.Pick@qmw.ac.uk> To: <freebsd-questions@FreeBSD.ORG> Sent: Thursday, July 01, 1999 7:32 PM Subject: Re: tcp wrappers > > > > But I can't see tcpd anywhere, only tcpdcheck and so on. Why is this ? > > > > If you look at the inetd manpage, you'll see that it supports builtin > > wrapping. You don't need tcpd. > > To be explicit - inetd is linked with the libwrap library so it's > unnecessary to activate a separate program with the extra overheads > that involves. > > > > What if I want to set up different access rules based on the protocol in = > > > use, not the program ? > > > > That's a limitation of hosts.allow. Short of creating a copy of the > > daemon binary with a new name, you can't do what you want to with inetd > > and TCP Wrappers. > > Actually, a separate copy is not necessary; a hard (or soft) link > is sufficient to make the wrappers see a new name so different rules > can be used. > > -- > David Pick > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00c801bec3e9$0cbd9560$2790ccc3>