identd permission denied to root!

[Sam20]

Hello,

What's denied to root here :

root#/opt# telnet localhost 113
Trying...
Connected to localhost.
Escape character is '^]'.
54217,7914
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
operation failed, Permission denied
pdirhash_type is 8.
Type 4 and 5 is not implemented yet (those are for obsolete OS)
Values other than 6,7 are suspicious and may be the result of a
core image from a running kernel that doesn't match the vmunix
This happen for instance when a machine panic after the kernel as been
regen'd but not yet rebooted
Continuing without translation
54217 , 7914 : ERROR : NO-USER
Connection closed by foreign host.

?!

Thx.

[SUDHAKAR_18]

check /etc/services for port no 113.

[Sam20]

The service is defined in /etc/services:
ident 113/tcp authentication # RFC1413

[Matti_Kurkela]

First, the fact that you run the telnet command as root does not guarantee that the identd is running as root. It might be running as some other user with reduced privileges (check /etc/inetd.conf for information on how identd is started).

Second, between the "Escape character is..." text and the port numbers you typed, the telnet command may send some data for telnet option negotiation. This data might be confusing identd: it might interpret the option negotiation data as one query, and the port numbers you typed as another query.

Third, the identd answer is not guaranteed to be printable. It might have contained some non-printable bytes that could have caused your terminal to dump some old data from its scroll-back buffer. So the error messages might originate from your local terminal emulator's memory, not from the identd.

If these messages are actually coming from identd, it would indicate a potentially security-sensitive bug in identd (it should not be sending out information that is unrelated to the ident protocol). Is your system up to date with patches?

MK