5 Star 1 Fork 1

Gitee 极速下载 / xinetd

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
此仓库是为了提升国内下载速度的镜像仓库,每日同步一次。 原始仓库: https://github.com/openSUSE/xinetd
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README

xinetd

Build Status

xinetd is a powerful replacement for inetd.

If you are planning to use xinetd on recent linux distribution also consider using systemd socket activation instead.

Original site (DEAD): http://www.xinetd.org

xinetd has access control mechanisms, extensive logging capabilities, the ability to make services available based on time, can place limits on the number of servers that can be started, and has deployable defence mechanisms to protect against port scanners, among other things.

There are a number of differences between xinetd and inetd. The largest difference to the end user is the config file. xinetd's config file format is more C like, and somewhat similar to bind 8's.

Access Control

xinetd keeps all the names you specify on the access control directives. When a client attempts to connect to a service, a reverse lookup is performed on the client's IP address. The canonical name returned is compared with the specified names. If the first character of the name being specified in the config file is a '.', then all hosts within that domain are matched. For example, if I put .synack.net, all hosts with a reverse mapping that are in .synack.net domain, are matched.

libwrap support

For libwrap access control, the access control is done by the server name for the service. So, if you have an entry like this: service telnet

{
	...
	server = /usr/sbin/in.telnetd
	...
}

Your corresponding hosts.{allow|deny} entry would look something like this:

in.telnetd: ALL

However, many services don't have a "server". Internal services and redirection services don't have a "server" line in the configuration file. Fma these services, the service name is used. For example:

server telnet
{
	...
	redirect = 10.0.0.1 23
	...
}

Your hosts.{allow|deny} entry would look something like this: telnet: ALL

So, in general, if a service has a "server" attribute to it, access control is performed based on that entry. If a service does not have a "server" attribute, (internal and redirection services) then access control is based on the service name. This is only for libwrap access control.

History

xinetd was originally written by panos@cs.colorado.edu. At least one other version of xinetd has been seen floating around the net. Another version is maintained by Rob Braun (bbraun@synack.net) and bug reports for that version should be directed to https://github.com/xinetd-org/xinetd/.

This version is simple collection of patches contained over Rob Brauns version that were present in all major distributions. Plans are to include fixes as required for keeping it workable in openSUSE and also to merge commits from the above github branch.

Issues

Bug reports/comments/suggestions/flames for this version should be sent to https://github.com/openSUSE/xinetd/issues/

空文件

简介

xinetd是新一代的网络守护进程服务程序,又叫超级Internet服务器,常用来管理多种轻量级Internet服务 展开 收起
取消

发行版

暂无发行版

贡献者

全部

近期动态

加载更多
不能加载更多了
C/C++
1
https://gitee.com/mirrors/xinetd.git
git@gitee.com:mirrors/xinetd.git
mirrors
xinetd
xinetd
master

搜索帮助

14c37bed 8189591 565d56ea 8189591