How Do I Enable IdentD?

I've already tried:

Ident Service Installer (Doesn't work at all)

IdentD 2.0 (installs, but can't activate)

IdentD 2.5.1 (installs, but can't activate)

In OS 9, this simply worked by degault. In OS X, unless is a Unix expert, it simply does NOT work.

If someone knows how to do this in Terminal, please give VERY SPECIFIC commands that can be copied and pasted.

Thanks in advance!

MDD 1gHz, Mac OS X (10.4.11)

Posted on Jul 16, 2009 10:40 PM

Reply
20 replies

Jul 17, 2009 7:21 PM in response to macarone112

Did you see this from zunipus...

I had IdentD bombing its server Start service over and over.

Solution that worked for me in 10.4.11 on an Intel MacBook:

In System Preferences I Ctrl-clicked on it's icon and selected 'Remove "IdentD" Preference Pane'. That tossed it in the Trash the official way. I then closed System Preferences and emptied the Trash.

I then specifically opened Port 113, as instructed in the installer Read Me, in my Mac OS X firewall and in my router, both TCP and UDP. In the case of my router I used port forwarding to my Mac's IP within my LAN.

At that point I reinstalled IdentD. After the installation was complete I opened System Preferences and opened the IdentD pane. I then hit the Activate button and all was well.


http://www.versiontracker.com/dyn/moreinfo/macosx/28564&vid=275508

Jul 17, 2009 11:25 PM in response to BDAqua

I have NO Firewall enabled. The computer I use for IRC has DMZ enabled in my router. No ports are "filtered". I have properly UNinstalled and reinstalled IdentD 2.0 and 2.5.1.

I have Googled this topic intensively. The only guyz that seem to be able to fix it are Unix/Terminal experts, and they never seem to give pricise instructions. They just send you to Terminal manual pages. for eg:

Am I missing something? It seemed like all he wanted to know is how to enable identd.
If so:

# The following are not known to be useful, and should not be enabled unless
# you have a specific need for it and are aware of the possible implemications.
#
#exec stream tcp nowait root /usr/libexec/tcpd rexecd
auth stream tcp wait root /usr/libexec/tcpd identd -w -t120

Change "ident" (the first word of the last line) to "auth" and you're good to go.


OR:

The problem is in a file called inetd.conf. Here's how you fix it, as described by Mike Vannorsdel in the forum thread:

Open a terminal session, and edit /etc/inetd.conf. Change the last line from

#ident stream tcp wait root /usr/libexec/tcpd identd -w -t120

to

auth stream tcp wait root /usr/libexec/tcpd identd -w -t120

Save the changes and reboot.



I am NOT the only one having this problem. There was a post by someone else with the same problem in the Leopard forum.

So, what I'm asking: could somebody check the above, and explain to a person like myself that bought his first Mac to do WORK, and to AVOID the command-line interface, how to enable identd.

Jul 18, 2009 5:44 PM in response to macarone112

I haven't done it myself, since I've no need for identd at the moment, but the instructions you posted above seem straightforward enough. Where do you anticipate you might run into problems?

If you want to check if identd has indeed been started and listening for connections, do the following from a Terminal prompt:

To check if it's running:
*ps aux |grep ident*

To check if it's listening:
*netstat -an -f inet |grep LISTEN*

Good luck.

Jul 19, 2009 12:03 AM in response to olaj

Let me restate the problem in greater detail:

I try to connect to an IRC server, here is the response:

Looking up IP number for newyork.ny.us.undernet.org
Connection with newyork.ny.us.undernet.org (49218) established
* Looking up your hostname
* Checking Ident
* No ident response
PING 1121185099
* Couldn't look up your hostname
* Ident broken or disabled

So I KNOW it's NOT working when I need it.

I've tried TWO different programs to get it working, and both have failed.

It works transparently without any problem when running OS 9.

I bought my first Mac (IIx) with 2 megs of ram and a 120 meg hard drive over 20 years ago, and it worked on THAT computer, and on every Mac since then INCLUDING the G4 MDD if it is booted into OS 9.

I can't get it to work on OS X.

Here are the results of your suggestion, which I don't understand at all:

mac-aldentes-power-mac-g4:~ macarone$ ps aux |grep ident
macarone 506 0.0 -0.0 18052 240 p1 R+ 2:20AM 0:00.00 grep ident
mac-aldentes-power-mac-g4:~ macarone$


mac-aldentes-power-mac-g4:~ macarone$ netstat -an -f inet |grep LISTEN
tcp4 0 0 *.1220 . LISTEN
tcp4 0 0 *.49156 . LISTEN
tcp4 0 0 *.80 . LISTEN
tcp4 0 0 *.8001 . LISTEN
tcp4 0 0 *.8000 . LISTEN
tcp4 0 0 *.7070 . LISTEN
tcp4 0 0 *.554 . LISTEN
tcp4 0 0 *.113 . LISTEN
tcp46 0 0 *.113 . LISTEN
tcp4 0 0 *.515 . LISTEN
mac-aldentes-power-mac-g4:~ macarone$


I've already reported that inspite of 20 years Mac experience, I was not able to make head or tail of the instructions from Unix experts on other forums. That's why I posted here, after first checking and finding that others have reported the same problem in the Leopard forum, and no solution was posted.

If, the information I posted here is useful, has anybody gotten it to work successfully? If so, please post STEP by STEP instructions, for eg:

1) Open Terminal and type:

pseudo gripes: enable: \off

2) Terminal should reply:

accepted

3) if instead it replies:

permission unavailable

4) type:

major /gripe .repeat


Now, I hope that at least the QUESTION is clear.

Thanks in advance to the kind soul that can help. I KNOW there are others that will be helped by this. And I DO know that Yahoo Messenger and MSN Messenger work without identd. I prefer to use IRC.

Jul 19, 2009 2:19 AM in response to olaj

From the netstat result you posted:
*tcp4 0 0 *.113 . LISTEN*
*tcp46 0 0 *.113 . LISTEN*

That means the ident/auth daemon is running and listening for connections from "everywhere," which is what you want.

For the next step, you can skip the Terminal. You need to punch a hole for port 113 on your firewall, assuming it's enabled. If it's not enabled and you still can't get the proper response on Undernet, then we're on to another level in troubleshooting.

Jul 19, 2009 2:33 AM in response to macarone112

Just saw your earlier post about not having any port filtered. Having your IRC machine on a DMZ isn't foolproof as far as fine-tuning connections is concerned. A small line of text in a config file or an overlooked option in router/firewall settings can throw stuff off track.

At this point all I can suggest is to hop on that particular machine, go to a site like grc.com which tests for open ports (use the Shields Up service) and confirm that port 113 on your network, through to your IRC machine, is indeed open.

Jul 19, 2009 7:30 PM in response to macarone112

Ok, so your ident/auth daemon is running, opening up port 113, and the port is open. At least that's clear.

What ident program are you using? Does it have a FAQ or Help section?
What IRC client are you using? Is it a console/terminal-based client or a graphical/GUI one?
Apart from Undernet, what other IRC networks do you want to use, if any?

Finally, why is ident all that important to you and your work? I use Undernet myself, and don't bother with it. Ident/auth is an archaic, outdated protocol that's always been a PITA, and I've always wondered why the Undernet admins insist on implementing it. It doesn't thwart connecting to a particular IRC server; it only slows the process down, and relegates you to a non-automated login; (good for giving malicious botnets a hard time) If you wait a while after trying to connect, you will get a prompt from Undernet informing you that "ident is broken" or some such, but after that it will give you something to type, and you can still connect after you manually type the requested text.

Jul 20, 2009 9:34 PM in response to olaj

Ok, so your ident/auth daemon is running


No, it is NOT running. It exists, but does NOT report my identd.



Is it a console/terminal-based client


I already admitted I was very uncomfortable using Terminal. I normally use ircle, I've tried Snak and Linkinus with similar results. Collquy does not work on my set up at all.


Ident/auth is an archaic, outdated protocol that's always been a PITA,


It may be a PITA to those trying to flood, run unauthorized bots etc. IRC and identd are almost as old as the internet. I'm trying to conform to current standards NOT to evade them. I'm trying to REVEAL my identity, not to hide it.

Jul 20, 2009 10:21 PM in response to macarone112

Not to quibble, but the daemon IS running; otherwise you have some ghostly program loose in your machine opening up the ident/auth port. Now, whether you've got it/your network configured right and it plays well with your network and with other ident servers is another matter altogether.

I asked what program you use. I can try duplicating what you're doing on my system when I find time. Maybe it'll help some.

Again, I maintain that aggravating yourself over getting ident to work properly is less important than getting on to the network in the first place.

Jul 22, 2009 6:40 PM in response to olaj

May we please get back on topic:

How Do I Enable IdentD? (By default is NOT AVAILABLE in Tiger)


When you log in to IRC, for eg. do you get:

* Processing connection to irc.xxxx.net
* Looking up your hostname...
* Checking Ident
* Found your hostname
* Got Ident response

Does your username appear WITHOUT a tilde (~) in front of it?

username@xxxxxxx OR is it: ~username@xxxxxxxx


If you cannot answer YES to BOTH of the above questions, you do NOT have identd enabled.


If you DO have identd enabled, you MUST have done something SPECIFIC, and I'm sure that ALL of the MANY people that have read this thread would appreciate clear, step by step instructions for NON-Unix-Terminal-Command line experts.

What is wanted is help from somebody that has done this successfully on OS X.4.11.

Aug 2, 2009 5:46 PM in response to macarone112

UPDATE

There have now been over 500 viewings of this topic. Even if this number represents only 100 people, each viewing 5 times to see replies, that still indicates serious interest.

I went into a Mac help chat channel with over 100 users logged in. Only a handful had identd running (NO tilde). I "versioned" these few, prior to messaging them for help, and EACH was using mIRC (meaning they were on Windows) OR they were using irssi or another Unix client. Rather a small sampling, but I couldn't find a SINGLE OS X user with identd.

This is just further proof that it IS a Mac OS X problem.

Is there really no solution?

Aug 2, 2009 11:42 PM in response to macarone112

You do realize that although irssi is a UNIX client, it too runs natively on the mac as well (after all, it is UNIX based) ? Wether that's downloading it via darwinports or compiling and installing it yourself from irssi's own website.

Anyways, I too many dark moons ago threw myself at attempting to enable identd on my OS X machine without much ultimate resolve. When I was running straight from an ethernet cable I did manage to make it run by opening port 113 on both ends and restarting identd, but after installing a router and running via ethernet/airport, it was a bust from that point onwards. Have you tried running ethernet directly from a adsl/cable modem instead of a router ?

I then ended up downloading the program IdentD for some GUI goodness, yet it only gave me a momentary fix, because after a few weeks it would refuse to authenticate and turn on period. I promptly gave up after that and never bothered 😍

Though I'm well over the issue (since i really don't need it to connect to any of my revered IRC servers) , I can't say this topic hasn't got my curiosity going a bit, however faintly 😝

Good luck !

- vasilios

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

How Do I Enable IdentD?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.