Bug 55192 - pidentd giving funny user names
pidentd giving funny user names
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: pidentd (Show other bugs)
7.2
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-10-26 16:49 EDT by mwalton
Modified: 2007-04-18 12:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-26 16:49:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description mwalton 2001-10-26 16:49:02 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2.1) Gecko/20010901

Description of problem:
I don't know for a fact that this is a pidentd but but I would guess that
it is. I just upgraded to redhat 7.2 and started irc. Whenever pidentd is
invoked it tells the remote server that I have some very strange user name
with what appears to be a random sequence of characters like (e.g.
[weOIJFdesd). The user name that it says I have is different each time. It
doesn't matter which irc client I run, and this only happens when the
relevant irc server acquires my username with identd.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Make sure identd daemon is started
2.start xchat or ircII and connect to some server that uses identd
3.look at your user name by typing /whois <your irc-nickname>
	

Actual Results:  My identity comes out as something like
[AefNOEef@home.cgocable.net.

Expected Results:  I should see hermes@home.cgocable.net

Additional info:
Comment 1 Trond Eivind Glomsrxd 2001-10-26 16:52:44 EDT
For privacy reasons, pident returns encrypted replies. Read docs if you want to
turn it off.

Note You need to log in before you can comment on or make changes to this bug.