From ArchWiki
Revision as of 13:53, 8 November 2013 by Roukoswarf (Talk | contribs) (Starting oidentd)

Jump to: navigation, search

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: please use the first argument of the template to provide a brief explanation. (Discuss in Talk:Oidentd#)

oidentd is an ident (rfc1413 compliant) daemon that runs on Linux, Darwin, FreeBSD, OpenBSD, NetBSD and Solaris. oidentd can handle IP masqueraded/NAT connections on Linux, Darwin, FreeBSD (ipf only), OpenBSD and NetBSD. oidentd has a flexible mechanism for specifying ident responses. Users can be granted permission to specify their own ident responses. Responses can be specified according to host and port pairs.


Install oidentd, available in the Official Repositories


With no global nor user configuration file(s), the users' ident replies will be that of their login name. This makes configuration files optional. See the oidentd.conf manual for more detail.

Global configuration

You may create the global configuration file /etc/oidentd.conf.

According to the manual, the following is suitable for a global configuration.

default {
     default {
          deny spoof
          deny spoof_all
          deny spoof_privport
          allow random
          allow random_numeric
          allow numeric
          allow hide
user root {
     default {
          force reply "UNKNOWN"

Which says, "Grant all users the ability to generate random numeric ident replies, the ability to generate numeric ident replies, and the ability to hide their identities on all ident queries. Explicitly deny the ability to spoof ident responses. And reply with `UNKNOWN' for all successful ident queries for root."

User configuration

Additionally and/or alternatively, each user may create his own local configuration file, $HOME/.oidentd.conf.

A possible example follows.

global { reply "unknown" }
to irc.example.org { reply "example" }

Which says, "Reply with `unknown' to all successful ident lookups, but reply with `example' to ident lookups for connections to irc.example.org."

The global configuration file will dictate what works in the user's local configuration file.

Starting oidentd

With oidentd installed and configured, you are now ready to start the daemon.

systemctl start oidentd.socket

If you want to have oidentd start up automatically every time you start your computer, then you need to enable oidentd.socket with systemd. For example:

systemctl enable oidentd.socket