Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 51588 - username sent to irc servers seems randomized
username sent to irc servers seems randomized
Product: Red Hat Public Beta
Classification: Retired
Component: pidentd (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Aaron Brown
Depends On:
  Show dependency treegraph
Reported: 2001-08-12 15:18 EDT by Christopher Stone
Modified: 2007-04-18 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-12 15:18:16 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Christopher Stone 2001-08-12 15:18:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010725

Description of problem:
When I log onto irc with BitchX, or my bot logs on using eggdrop, the user
name field seems corrupted.  For example my hostname is
[EiFfqdExD@adsl-63-201-24-182.dsl.renocs.nvbell.net and a whoami command
returns chris

How reproducible:

Steps to Reproduce:
1.  Log onto an IRC server (I'm using EFNET)
2.  Run a /whois command on yourself and check your user name in your hostname
3.  Username is randomized

Actual Results:  incorrect hostname sent to irc server

Expected Results:  username should match that of the whoami command

Additional info:

Started happening when I upgraded to Roswell
Comment 1 Trond Eivind Glomsrxd 2001-08-12 20:44:04 EDT
The default configuration sends an encrypted reply, for privacy reasons. The
string can be decrypted by a sysadmin when asked by a remote site to do so -
there's no reason to send a username in the clear. Read the docs if you want to
change the behaviour.

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