Setting up Identd server on Slack 10.0

LOLobo · 07-10-2005, 04:08 AM

I've been doing this -->

(RTFM)
and now I'm doing this -->

I have four workstations all on a router. One of them (a Windows XP box), is running a piece of freeware I found that functions as an Identd server for all workstations on my network...

I want to stop using it. I would like for my Slack box to run an Ident(d) server for the network, since I have up to three workstations accessing IRC at the same time. Currently, with the Windows XP set-up, all if functioning well. However, I am having a very hard time figuring it out without a set-by-step on how to get this to function ON A SLACKWARE BOX specifically.

I have tried Oident, with complete failure. I'm willing to try the software again, but I really need a complete HOWTO. I am willing to try other packages as well, or if there is some type of config that I need to change...

I just want to run an ident server.

Thanks, in advance, to anyone that replies.

gbonvehi · 07-10-2005, 05:05 AM

Slackware comes by default with a indetd server, it's started by the inetd daemon as stated on /etc/inetd.conf, look for a line that says:
auth stream tcp wait root /usr/sbin/in.identd in.identd
and make sure it doesn't have a # at the beggining.

Then restart inetd with: /etc/rc.d/rc.inetd restart

Make sure you've the pidentd package that comes with Slackware, it's the inetd server. You can get the package online here: http://slackware.it/en/pb/searchfile...in.identd&w=on

LOLobo · 07-10-2005, 08:06 PM

I do have the pidentd package installed (I guessed it is pre-installed with Slack 10.0).

I also uncommented the line which you spoke of in /etc/inetd.conf.

I guess my last task was to edit /etc/identd.conf so that it would give an "ident response" to IRC.

That's where I am currently stuck at. :scratch:

This is what my current /etc/identd.conf looks like. Please, someone tell me if I have a missed setting, need to uncomment something, or if I'm off in a completely wrong direction.

Code:

# /etc/identd.conf - an example configuration file


#-- The syslog facility for error messages
 syslog:facility = daemon


#-- User and group (from passwd database) to run as
server:user = nobody

#-- Override the group id
# server:group = kmem

#-- What port to listen on when started as a daemon or from /etc/inittab
 server:port = 113

#-- The socket backlog limit
# server:backlog = 256

#-- Where to write the file containing our process id
server:pid-file = "/var/run/identd.pid"

#-- Maximum number of concurrent requests allowed (0 = unlimited)
 server:max-requests = 0

#-- Enable some protocol extensions like "VERSION" or "QUIT"
# protocol:extensions = enabled

#-- Allow multiple queries per connection. This slightly breaks RFC1413
# protocol:multiquery = enabled

#-- Timeout in seconds since connection or last query. Zero = disable
 protocol:timeout = 5

#-- Maximum number of threads doing kernel lookups
# kernel:threads = 8

#-- Maximum number of queued kernel lookup requests
 kernel:buffers = 32

#-- Maximum number of time to retry a kernel lookup in case of failure
 kernel:attempts = 5

#-- Disable username lookups (only return uid numbers)
# result:uid-only = no

#-- Enable the ".noident" file
# result:noident = enabled

#-- Charset token to return in replies
 result:charset = "US-ASCII"

#-- Opsys token to return in replies
 result:opsys = "UNIX"

#-- Log all request replies to syslog (none == don't)
# Valid choices are: none, debug, info, notice, warning, err, crit, emerg
result:syslog-level = notice

#-- Enable encryption (only available if linked with a DES library)
# result:encrypt = no

#-- Path to the DES key file (only available if linked with a DES library)
# encrypt:key-file = "/etc/identd.key"

#-- Include a machine local configuration file
 include = /usr/local/etc/identd.conf

gbonvehi · 07-10-2005, 11:05 PM

That's weird, I remember identd working with the default config, never touched the file.
Anyway, since I read that the IRC servers I was using didn't need identd identification I simply disabled the daemon.

LOLobo · 07-14-2005, 11:39 PM

I ended up installing a BNC that had a piece of software for ident called mdidentd....

I finally got it working by forcing it to give a fake ident at every connection....

The name of the software was EZBounce. Wound up working nicely, plus I now have my own BNC.

Thanks iGZo!!!