Closed
Bug 824843
Opened 13 years ago
Closed 1 year ago
Client tries to steal other user's nickname in conversation
Categories
(Other Applications Graveyard :: ChatZilla, defect)
Other Applications Graveyard
ChatZilla
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: honza.hron, Assigned: rginda)
References
Details
(Keywords: regression)
When you open a conversation with another user, click on the nickname button and select Change nickname, the client apparently tries to steal the nickname of the conversation partner.
Instead of the usual prompt where one can change their nickname, following message appears in the conversation:
=== The nickname “NickName” is already in use, use the /nick command to pick a new one.
Comment 2•13 years ago
|
||
(In reply to Gryllida from comment #1)
> I can confirm this behaviour.
Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17a1 ID:20121219180903 c-c:68dcb9af22fb m-c:21195f52311c
me too, and also on L64 trunk.
Hardware: x86 → All
Version: unspecified → Trunk
Comment 3•13 years ago
|
||
P.S. When in a query with NickServ (or ChanServ or MemoServ etc.) the message is different but the phenomenon is the same:
NickServ Erroneous Nickname: Reserved for Services
meaning cZ tried (and failed) to change its nick to "NickServ".
Comment 4•13 years ago
|
||
This is caused by the patch for Bug 450309, specifically the lines in static.js that define rv.nickname to be rv.userName.
Updated•13 years ago
|
Blocks: 450309
Keywords: regression
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
Updated•1 year ago
|
Product: Other Applications → Other Applications Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•