Партнёры:
Хостинг:
inetd - internet ``super-server''
The following options are available:
When the hostname specification is used and both IPv4 and IPv6 bindings are desired, one entry with the appropriate protocol type for each binding is required for each service in /etc/inetd.conf For example, a TCP-based service would need two entries, one using ``tcp4'' for the protocol and the other using ``tcp6'' See the explanation of the /etc/inetd.conf protocol field below.
Upon execution, reads its configuration information from a configuration file which, by default, is /etc/inetd.conf There must be an entry for each field of the configuration file, with entries for each field separated by a tab or a space. Comments are denoted by a ``#'' at the beginning of a line. There must be an entry for each field. The fields of the configuration file are as follows:
service-name
socket-type
protocol
{wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]
user[:group][/login-class]
server-program
server-program-arguments
To specify an ONC RPC -based service, the entry would contain these fields:
service-name/version
socket-type
rpc/protocol
{wait|nowait}[/max-child[/max-connections-per-ip-per-minute[/max-child-per-ip]]]
user[:group][/login-class]
server-program
server-program-arguments
There are two types of services that can start: standard and TCPMUX. A standard service has a well-known port assigned to it; it may be a service that implements an official Internet standard or is a BSD -specific service. As described in RFC 1078 TCPMUX services are nonstandard services that do not have a well-known port assigned to them. They are invoked from when a program connects to the ``tcpmux'' well-known port and specifies the service name. This feature is useful for adding locally-developed servers. TCPMUX requests are only accepted when the multiplexor service itself is enabled, above and beyond and specific TCPMUX-based servers; see the discussion of internal services below.
The service-name entry is the name of a valid service in the file /etc/services or the specification of a UNIX domain socket (see below). For ``internal'' services (discussed below), the service name should be the official name of the service (that is, the first entry in /etc/services ) When used to specify an ONC RPC -based service, this field is a valid RPC service name listed in the file /etc/rpc The part on the right of the ``/'' is the RPC version number. This can simply be a single numeric argument or a range of versions. A range is bounded by the low version to the high version - ``rusers/1-3'' For TCPMUX services, the value of the service-name field consists of the string ``tcpmux'' followed by a slash and the locally-chosen service name. The service names listed in /etc/services and the name ``help'' are reserved. Try to choose unique names for your TCPMUX services by prefixing them with your organization's name and suffixing them with a version number.
The socket-type should be one of ``stream'' ``dgram'' ``raw'' ``rdm'' or ``seqpacket'' depending on whether the socket is a stream, datagram, raw, reliably delivered message, or sequenced packet socket. TCPMUX services must use ``stream''
The protocol must be a valid protocol or ``unix'' Examples are ``tcp'' or ``udp'' both of which imply IPv4 for backward compatibility. The names ``tcp4'' and ``udp4'' specify IPv4 only. The names ``tcp6'' and ``udp6'' specify IPv6 only. The names ``tcp46'' and ``udp46'' specify that the entry accepts both IPv4 and IPv6 connections via a wildcard AF_INET6 socket. Rpc based services are specified with the ``rpc/tcp'' or ``rpc/udp'' service type. One can use specify IPv4 and/or IPv6 with the 4, 6 or 46 suffix, for example ``rpc/tcp6'' or ``rpc/udp46'' TCPMUX services must use ``tcp'' ``tcp4'' ``tcp6'' or ``tcp46''
The wait/nowait entry specifies whether the server that is invoked by will take over the socket associated with the service access point, and thus whether should wait for the server to exit before listening for new service requests. Datagram servers must use ``wait'' as they are always invoked with the original datagram socket bound to the specified service address. These servers must read at least one datagram from the socket before exiting. If a datagram server connects to its peer, freeing the socket so can receive further messages on the socket, it is said to be a ``multi-threaded'' server; it should read one datagram from the socket and create a new socket connected to the peer. It should fork, and the parent should then exit to allow to check for new service requests to spawn new servers. Datagram servers which process all incoming datagrams on a socket and eventually time out are said to be ``single-threaded'' The comsat(8) and talkd(8) utilities are examples of the latter type of datagram server. The tftpd(8) utility is an example of a multi-threaded datagram server.
Servers using stream sockets generally are multi-threaded and use the ``nowait'' entry. Connection requests for these services are accepted by , and the server is given only the newly-accepted socket connected to a client of the service. Most stream-based services operate in this manner. Stream-based servers that use ``wait'' are started with the listening service socket, and must accept at least one connection request before exiting. Such a server would normally accept and process incoming connection requests until a timeout. TCPMUX services must use ``nowait''
The maximum number of outstanding child processes (or ``threads'' for a ``nowait'' service may be explicitly specified by appending a ``/'' followed by the number to the ``nowait'' keyword. Normally (or if a value of zero is specified) there is no maximum. Otherwise, once the maximum is reached, further connection attempts will be queued up until an existing child process exits. This also works in the case of ``wait'' mode, although a value other than one (the default) might not make sense in some cases. You can also specify the maximum number of connections per minute for a given IP address by appending a ``/'' followed by the number to the maximum number of outstanding child processes. Once the maximum is reached, further connections from this IP address will be dropped until the end of the minute. In addition, you can specify the maximum number of simultaneous invocations of each service from a single IP address by appending a ``/'' followed by the number to the maximum number of outstanding child processes. Once the maximum is reached, further connections from this IP address will be dropped.
The user entry should contain the user name of the user as whom the server should run. This allows for servers to be given less permission than root. The optional group part separated by ``:'' allows a group name other than the default group for this user to be specified. The optional login-class part separated by ``/'' allows specification of a login class other than the default ``daemon'' login class.
The server-program entry should contain the pathname of the program which is to be executed by when a request is found on its socket. If provides this service internally, this entry should be ``internal''
The server-program-arguments entry lists the arguments to be passed to the server-program starting with argv[0], which usually is the name of the program. If the service is provided internally, the service-name of the service (and any arguments to it) or the word ``internal'' should take the place of this entry.
Currently, the only internal service to take arguments is ``auth'' Without options, the service will always return ``ERROR : HIDDEN-USER'' The available arguments to this service that alter its behavior are:
The utility also provides several other ``trivial'' services internally by use of routines within itself. These services are ``echo'' ``discard'' ``chargen'' (character generator), ``daytime'' (human readable time), and ``time'' (machine readable time, in the form of the number of seconds since midnight, January 1, 1900). All of these services are available in both TCP and UDP versions; the UDP versions will refuse service if the request specifies a reply port corresponding to any internal service. (This is done as a defense against looping attacks; the remote IP address is logged.) For details of these services, consult the appropriate RFC document.
The TCPMUX-demultiplexing service is also implemented as an internal service. For any TCPMUX-based service to function, the following line must be included in inetd.conf
tcpmux stream tcp nowait root internal
When given the -l option will log an entry to syslog each time a connection is accepted, noting the service selected and the IP-number of the remote requester if available. Unless otherwise specified in the configuration file, and in the absence of the -W and -w options, will log to the ``daemon'' facility.
The utility rereads its configuration file when it receives a hangup signal, SIGHUP Services may be added, deleted or modified when the configuration file is reread. Except when started in debugging mode, or configured otherwise with the -p option, records its process ID in the file /var/run/inetd.pid to assist in reconfiguration.
Note that only wraps requests for a ``wait'' service while no servers are available to service requests. Once a connection to such a service has been allowed, has no control over subsequent connections to the service until no more servers are left listening for connection requests.
When wrapping is enabled, the tcpd daemon is not required, as that functionality is builtin. For more information on TCP Wrappers, see the relevant documentation (hosts_access5 ) When reading that document, keep in mind that ``internal'' services have no associated daemon name. Therefore, the service name as specified in inetd.conf should be used as the daemon name for ``internal'' services.
If the TCPMUX service name begins with a ``+'' returns the positive reply for the program. This allows you to invoke programs that use stdin/stdout without putting any special server code in them.
The special service name ``help'' causes to list the TCPMUX services which are enabled in inetd.conf
If an invalid IPsec policy specifier appears in inetd.conf will provide an error message via the syslog(3) interface and abort execution.
":news:daemon:220:/var/run/sock"
creates a socket owned by user ``news'' in group ``daemon'' with permissions allowing only that user and group to connect. The default owner is the user that is running as. The default mode only allows the socket's owner to connect.
WARNING while creating a UNIX domain socket, must change the ownership and permissions on the socket. This can only be done securely if the directory in which the socket is created is writable only by root. Do NOT use to create sockets in world writable directories such as /tmp use /var/run or a similar directory instead.
Internal services may be run on UNIX domain sockets, in the usual way. In this case the name of the internal service is determined using the last component of the socket's pathname. For example, specifying a socket named /var/run/chargen would invoke the ``chargen'' service when a connection is received on that socket.
ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l ntalk dgram udp wait root /usr/libexec/ntalkd ntalkd telnet stream tcp6 nowait root /usr/libexec/telnetd telnetd shell stream tcp46 nowait root /usr/libexec/rshd rshd tcpmux/+date stream tcp nowait guest /bin/date date tcpmux/phonebook stream tcp nowait guest /usr/local/bin/phonebook phonebook rstatd/1-3 dgram rpc/udp wait root /usr/libexec/rpc.rstatd rpc.rstatd /var/run/echo stream unix nowait root internal #@ ipsec ah/require chargen stream tcp nowait root internal #@
Use the -R rate option, as described above, to change the rate limit. Once the limit is reached, the service will be reenabled automatically in 10 minutes.
|
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |