ident in linux

[Barnaby W. Füi]

now that my usual irc server is gone and i am going back to efnet for amusement, i have to install ident.

i looked at linuxdocs and found a few recommendations, first one was oident. so i downloaded and installed it, but now what?

the readme doesnt have any specific info about using oident, and the INSTALL file only says how to install it (./configure, make, make install, WOW thats helpful), and lots of info for using it on bsd, solaris, etc. it does not say what to do AFTER you install it. it installed to /usr/local/sbin, i try to run it, and it says "bash: not a valid command" or whatever. so i cd there and do a ./oident. this happens:

[Bitch@c1816619-b sbin]$ ./oidentd
[Bitch@c1816619-b sbin]$

so i'm thinking that it ran or whatever now. but still efnet wont let me on saying i dont have ident.

so....wtf do i do? it is a daemon, which i sort of know is something that runs behind the scenes, like a service in NT right? and it did say somewhere in the INSTALL or README that it doesnt need to be added to any configuration file or anything like that.

so............??????????

 

[n0cmonkey]

identd usually runs from inetd (xinetd if you use RedHat). So look into setting it up in /etc/xinetd.conf or whatever.

 

[Barnaby W. Füi]

#
# Simple configuration file for xinetd
#
# Some defaults, and include /etc/xinetd.d/

defaults
{
instances = 60
log_type = SYSLOG authpriv
log_on_success = HOST PID
log_on_failure = HOST
cps = 25 30
}

includedir /etc/xinetd.d




that is my xinetd.conf.

what do i add to it?

 

[n0cmonkey]

man xinetd.conf

I dont use redhat so I havent looked into xinetd. But it looks like there are config scripts in /etc/xinetd.d. Just a guess though.

 

[Barnaby W. Füi]

excuse my lack of intelligence but the man page was less than helpful

in inetd.d there was a bunch of stuff:

[Bitch@c1816619-b xinetd.d]$ ls
chargen daytime-udp finger rlogin talk time-udp
chargen-udp echo ntalk rsh telnet wu-ftpd
daytime echo-udp rexec rsync time

looking at those files was not very informative, either.

the ironic thing is at linuxdocs it says something like "installing ident is beyond the scope of this document but each client will contain its own documentation"

laugh

EDIT: you know you would think something as simple as ident would be easier than this or at least would have more documentation.

i've searched google and all the results were total crap.

 

[n0cmonkey]

paste the finger file for me. Maybe I can make sense of it

 

[Barnaby W. Füi]

# default: on
# description: The finger server answers finger requests. Finger is \
# a protocol that allows remote users to see information such \
# as login name and last login time for local users.
service finger
{
socket_type = stream
wait = no
user = nobody
server = /usr/sbin/in.fingerd
disable = yes
}



--hehe it says fingerd

 

[n0cmonkey]

<< # default: on
# description: The finger server answers finger requests. Finger is \
# a protocol that allows remote users to see information such \
# as login name and last login time for local users.
service finger
{
socket_type = stream
wait = no
user = nobody
server = /usr/sbin/in.fingerd
disable = yes
}



--hehe it says fingerd >>



service ident
{
socket_type = stream
wait = no
user = nobody
server = /usr/local/oidentd
disable = no
}

Maybe something like that...

 

[Barnaby W. Füi]

and name the file ident?

 

[n0cmonkey]

<< and name the file ident? >>



Yeah. Im not sure it will work.. See if there is a manpage for oidentd. It may tell you if there are any flags it should need. And I may have gotten the wrong idea for the setup I pasted...

 

[Barnaby W. Füi]

the man page says nothing about needing any specific flags

didnt work

 

[n0cmonkey]

You dont have a firewall or anything setup in /etc/hosts.deny do you?

 

[Barnaby W. Füi]

nope i have nothing (manually) yet in regards to a firewall or iptables or anything.

 

[n0cmonkey]

Check to make sure nothing is in /etc/hosts.deny (if you havent already). Is this machine connected directly to the net or is it behind a router or anything? Internal ip or external? Is xinetd running? If so, did you kill HUP it? Find the PID and then "kill -HUP PID". Forgot that step. Its important for inetd, but I dont know much about xinetd

 

[Barnaby W. Füi]

<< Check to make sure nothing is in /etc/hosts.deny (if you havent already). >>


woah, that might be it, it was ALL:ALL.


<< Is this machine connected directly to the net or is it behind a router or anything? Internal ip or external? >>


no router or anything, just cable modem --> computer so external ip.


<< Is xinetd running? If so, did you kill HUP it? Find the PID and then "kill -HUP PID". Forgot that step. Its important for inetd, but I dont know much about xinetd >>


Huh? Ok i will do that only if you abc your lmnop. heh, sorry you gotta dumb it down a little

 

[n0cmonkey]

<<

<< Check to make sure nothing is in /etc/hosts.deny (if you havent already). >>


woah, that might be it, it was ALL:ALL. >>



That should keep it from working unless you add something into hosts.allow to allow ident traffic. Something like ALL:113 or 113:ALL I cant remember.



<<

<< Is this machine connected directly to the net or is it behind a router or anything? Internal ip or external? >>


no router or anything, just cable modem --> computer so external ip.


<< Is xinetd running? If so, did you kill HUP it? Find the PID and then "kill -HUP PID". Forgot that step. Its important for inetd, but I dont know much about xinetd >>


Huh? Ok i will do that only if you abc your lmnop. heh, sorry you gotta dumb it down a little >>



Bwahahahaha! Anyhow, ps -auxww | grep xinetd, get the pid (process id), then kill -HUP pid using the process ID for xientd. -HUP usually means reread the configuration file for that program. It may not work with xinetd, but it couldnt really hurt

 

[Barnaby W. Füi]

[Bitch@c1816619-b data]$ ps -auxww | grep xinetd
root 789 0.0 0.1 2268 960 ? S 20:25 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid

which one is the pid?

 

[n0cmonkey]

789 I believe. But Im not positive.. ps can act differently between UNIXes...

 

[Barnaby W. Füi]

killed it, still the same

damn this sucks

 

[n0cmonkey]

<< killed it, still the same

damn this sucks >>



And you edited the /etc/hosts.allow? Hell, if you cant find anything on any of the sites out there, just connect to prison.net.

 

[Barnaby W. Füi]

ah been eatin

i just commented the ALL:ALL in hosts.deny, which i'm sure is a bad thing but i just did it when testing this out.

that would have the same effect as adding to hosts.allow right?

hey i never knew about prison.net

i always use lightning.net or occasionally efnet.org

(edit): commented not uncommented

 

[n0cmonkey]

The ALL:ALL in hosts.deny keeps anyone from connecting to your machine. Atleast the things in xinetd or if they are compiled with certain libraries. Any of it work?

 

[Barnaby W. Füi]

ok back at it again....i uncommented the ALL:ALL in hosts.deny again, so it is how it originally was and changed hosts:allow to say 113:ALL, did a kill -HUP and still didnt work. changed 113:ALL to ALL:113 and did kill -HUP and still didnt work.

damn :|

 

[Nothinman]

service ident
{
socket_type = stream
protocol = tcp
wait = no
user = nobody
server = /usr/sbin/oidentd
server_args = -i -m
}

Works for me on my Debian box, putting this in a /etc/xinetd.d/ident should do it although I just have that in my /etc/xinetd.conf file. Remove the -m part if you don't want it to masquerade (lie) for you.

 

[Barnaby W. Füi]

ok nothinman i copied your example except the -m, tried it, didnt work. also in hosts.allow should it be 113:ALL or ALL:113? i tried both, and did kill -HUPs each time and still nothing:|