From: panos@burton.cs.colorado.edu (Panos Tsirigotis)
Subject: Re: inetd.syslog ?
Organization: University of Colorado, Boulder
Date: Tue, 15 Dec 1992 19:53:41 GMT

In article <1992Dec14.174924.751@sun1.ruf.uni-freiburg.de> kleinren@sun1.ruf.uni-freiburg.de (Rainer Kleinrensing) writes:
>Hello there,
>we are running a SPARCstation 10 Model 20 with SUNOS 4.1.3
>I am looking for a modified version of inetd that will log
>ALL requests via syslog. This has been implemented on Convex machines, for
>example:
>Dec 14 17:53:04 sfb256 inetd[24006]: Req: login From: 131.220.223.205 
>Dec 14 17:56:35 sfb256 inetd[24006]: Req: finger From: 131.220.223.1 
>Dec 14 18:01:03 sfb256 inetd[24006]: Req: shell From: 131.220.223.12 
>Dec 14 18:11:38 sfb256 inetd[24006]: Req: telnet From: 131.220.132.2 
>
>Is such a modified inetd available, either pd or commercial ?
>Thanks a lot,
>

I am sure a lot of people will have mentioned the tcp_wrapper software.
Here is another alternative, more close to what the original request
was: I have written a new inetd (called xinetd for eXtented inetd)
and here is what it can do:

      1) Access control on all services based on:
            a. address of remote host
            b. time of access

      2) Extensive logging abilities:
            a. for every server started it can log:
                    i) the time when the server was started
                   ii) the remote host address
                  iii) who was the remote user (if the other end runs a
                       RFC931 server)
                   iv) how long the server was running
               (i, ii and iii can be logged for failed attempts too).
            b. for some services, if the access control fails, it can
               log information about the attempted access (for example,
               it can log the user name and command for the rsh service)

      3) It provides hard reconfiguration:
            a. kills servers for services that are no longer in the
               configuration file
            b. kills servers that no longer meet the access control criteria

      4) No limit on number of server arguments

      5) Access control works on all services, whether multi-threaded or
         single-threaded and for both the TCP and UDP protocols.
         All UDP packets can be checked as well as all TCP connections.

      6) It can prevent denial-of-access attacks by
            a. placing limits on the number of servers for each service
            b. placing an upper bound on the number of processes it will fork
            c. placing limits on the size of log files it creates

I have been using xinetd on my Sun IPC for some months now without
any problems.

You can get the software by anonymous ftp from mystique.cs.colorado.edu,
in the directory pub/xinetd. BTW, I am using xinetd to enforce a
ftp server limit of 4 (i.e. no more than 4 ftpd's running at the same time)
so if you can't connect to mystique that's probably the reason.

Panos

-- 
Panos Tsirigotis, CS grad                        
Pmail: Computer Science Dept., U. of Colorado @ Boulder, Boulder, CO 80309-0430
Email: panos@cs.colorado.edu
Newsgroups: comp.sys.sun.wanted,comp.sys.sun.hardware,comp.sys.sun.misc