oidentd is an RFC 1413 compliant ident daemon which runs on Linux, FreeBSD, NetBSD, Darwin, OpenBSD, and Solaris. It can handle IP masqueraded/NAT connections on Linux, FreeBSD, NetBSD, and OpenBSD, and it 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.
| Tags | Networking |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX BSD FreeBSD OpenBSD Linux Solaris |
| Implementation | C |


Release Notes: Bugfixes and build fixes for Solaris.


Release Notes: Support for inetd has been re-added. Build errors on FreeBSD and Darwin have been fixed.


Release Notes: This release fixed bugs in the IPv6 code, compilation, and connection forwarding under BSD. It also added support for FreeBSD 5, DNAT support for Linux, and support for connection forwarding on recent versions of OpenBSD. Some other bugs were also fixed.


Release Notes: This release has support for faster lookups on Linux using netlink, and support for NetBSD, Darwin, and Solaris 9. Various bugs have been fixed.


Release Notes: A compile bug on OpenBSD 3.0 was fixed.
01 Aug 2007 05:29
IPv6 only??
i'm using it on kubuntu gutsy gibbon alpha3
apparently it only listens on IPv6 and i need IPv4.
root@patrick-desktop:/var/log# netstat -a | grep auth
tcp6 0 0 *:auth *:* LISTEN
05 Mar 2006 08:16
Re: psybnc+oidentd issue resolved - plz ignore last post
Well my oidentd apparently can't use the spoof function on a FreeBSD 5.4 box.. The config files are the following
oidentd.conf
default {
default {
deny spoof
deny spoof_all
deny spoof_privport
allow random_numeric
deny hide
}
}
user phyre {
default {
allow spoof
allow spoof_all
allow spoof_privport
}
}
And my .oidentd.conf in the phyre home directory :
global { reply "phyre" "forsaken" "jupiter" "schatje"}
So on IRC for example, the IRC client reports
phyre@phyre.cc like it should, instead of ~phyre@phyre.cc
But when I use an eggdrop bot on IRC, and try to spoof the username to 'jupiter', the .oidentd.conf
file seems to be neglected by the daemon...
Any ideas anyone because I've ran out of them...
Cheers!
07 Oct 2004 12:49
Re: psybnc+oidentd issue resolved - plz ignore last post
My wont work even when I did like you, but can you say more exactly how you did all the way and that version is you using ?
25 Aug 2004 14:41
psybnc+oidentd issue resolved - plz ignore last post
I figured out my STUPID problem. When you run oidentd as -u nobody and -g nobody, it doesn't have access to the /home/*/.oidentd.conf files until you give chmod o+rx /home/* and chmod o+r /home/*/.oidentd.conf files... This non-issue is resolved. I hope everyone else is 1) not as stupid as I am, or 2) able to use this info to learn from my mistake.
25 Aug 2004 08:54
oidentd and psybnc
I don't understand what needs to happen for psybnc to use oidentd correctly.
oidentd (on my psybnc server) does not pick up my irc client's ident response, or use the psybnc username/nickname/login for it's ident response.
Additionally, oidentd returns the username that started the psybnc process to irc servers (psybnc-process-starter) and completely ignores /home/(psybnc-process-starter)/.oidentd.conf.
This is on a RHL 7.3 system.
My /etc/oidentd.conf command is as follows:
default {
default {
allow spoof
deny spoof_all
deny spoof_privport
allow random
allow random_numeric
allow numeric
deny hide
}
}
And the command I use to start oidentd is as follows:
oidentd -d -m -f -u nobody -g nobody -C /etc/oidentd.conf
What is wrong here? psybnc has been compiled with oidentd support flagged, so that is not the problem.
The psybnc process on the redhat system has multiple users that connect on virtual ips (it is a virtually multi-homed system) (/etc/sysconfig/network-scripts/ifcfg-eth0:1, eth0:2, etc.).