Comments for oidentd
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.).
10 Oct 2003 10:47
Re: oidentd 2.0.7
> running oidentd 2.0.7 on slack 9.x with
> 2.4.20
>
> getting:
> [129.250.228.2] 54890 , 6667 : ERROR :
> NO-USER
>
> even when logged in as root, or any
> user
>
> oidentd -l 5 -e --other=UNIX
>
> is what i used to start it,
>
> oidentd -l 5 -u nobody -e --other=UNIX
> -r MYSTRING
>
> is what i normally use to run it, but
> all the sudden it just stopped
> responding when i had a power outage,
> and the box lost power. nothing else on
> the box seems to have problems, but
> oidentd. it will respond to all queries
> with MYSTRING, even for a local ircd
> request. the box is behind a router, but
> running as DMZ, even with port 113
> forwarded to the box, the samething
> happens.
>
Hi freak,
I have your same problem.. did u solved it?
22 Aug 2003 16:43
Solaris
2.0.7 fails to compile on Solaris 7
15 Aug 2003 09:08
oidentd 2.0.7
running oidentd 2.0.7 on slack 9.x with 2.4.20
getting:
[129.250.228.2] 54890 , 6667 : ERROR : NO-USER
even when logged in as root, or any user
oidentd -l 5 -e --other=UNIX
is what i used to start it,
oidentd -l 5 -u nobody -e --other=UNIX -r MYSTRING
is what i normally use to run it, but all the sudden it just stopped responding when i had a power outage, and the box lost power. nothing else on the box seems to have problems, but oidentd. it will respond to all queries with MYSTRING, even for a local ircd request. the box is behind a router, but running as DMZ, even with port 113 forwarded to the box, the samething happens.
15 Apr 2003 01:27
Re: oidentd + FreeBSD + ipf
I just installed oidentd with an IPF enabled kernel, and all works well for me. Are you starting oidentd with the flags '-f -m'? -f == forwarding, and falls back to -m for masquerading support in /etc/oidentd_masq.cfg
> Oidentd isn't working properly on
> FreeBSD with ipf enabled.
>
> --Configuration
>
> checking if nat_t has nat_p member...
> NO
> MASQ disabled
>
> i check configure script, and found
> points. Script search within
> /usr/local/include for 3 headers. But
> that headers isn't there. OK. Problem
> resolved. I copy this headers from
> /usr/src/... to this path. And configure
> again. And see
> checking if nat_t has nat_p member...
> YES. Great!!! But oidentd is still not
> working through IPNAT. It is bug or
> something ? Oidentd is only one which
> support masqueraded connections.
> Configuration of my BSD box is:
>
>
> FreeBSD jankolova.ovsiste.sk 4.8-RC
> FreeBSD 4.8-RC #2: Wed Mar 5 12:13:39
> CET 2003
> root@jankolova.ovsiste.sk:/usr/obj/usr/src/sys/solko_ipf
> i386
>
> with ipf enabled :)
>
27 Mar 2003 02:32
cygwin compiling...
ok downloaded and tried to compile on cygwin (win98se, 1.3.22) 3 versions now and with ./configure i get a start but it ends all the time with "cygwin not yet supported" so my question is... when is gonna be supported? :)
i hope soon enough...
ciao,
Valentin
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