View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000482 | unreal | ircd | public | 2002-11-27 00:24 | 2003-11-20 19:46 |
| Reporter | simonbell | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.2-beta12 | ||||
| Summary | 0000482: Hostile Username problem | ||||
| Description | A user with the address: [email protected] attempts to connect to either of our 2 3.2beta12-win32-ssl servers (running win2kserver) but always gets this error: *** Error: Closing Link: GrUnGeR[pc2-glfd1-6-cust46.glfd.cable.ntl.com] (Hostile username. Please use only 0-9 a-z A-Z _ - and . in your username.) The problem is, as far as we can see his username does not contain these invalid characters, and more importantly, he can connect to both of our linux servers with no trouble at all, also running 3.2beta12, so it seems like it could be a bug. We do not see anything relating to this in the status window, the user's connection does not appear at all. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Ok well the *** Error: Closing Link: GrUnGeR[pc2-glfd1-6-cust46.glfd.cable.ntl.com] (Hostile username. Please use only 0-9 a-z A-Z _ - and . in your username.) The GrUnGeR there is NOT his username, that is his nickname. For example I just tested connecting with asdf!&*&*@myhost.com it says: ERROR :Closing Link: asdf[myhost.com] (Hostile username. Please use only 0-9 a-z A-Z _ - and . in your username.) asdf is the nickname, not the username. Now I have a theory about how this happened, when the user is connecting to the win32 ssl server his ident didn't resolve, so say his 'username' (not ident) is set to &*&*. That means when he connects to your server he will be banned. But if his ident is GrUnGeR that means if his ident does resolve then there is no issue, that is a perfectly valid username. lastly "A user with the address: [email protected] attempts to connect" I'm assuming you obtained this from when he successfully connected to another server? Because you do not get a +c notice if he is banned with a hostile name. So if that is the case it only further goes to prove what I have said, that he has his username set to something invalid but his ident set to something valid. |
|
|
OK The [email protected] is from a /whois i did on this particular user on 2 different irc networks where he can connect without a problem. If this is the problem, where does he change his 'username' in his mirc settings? i see ident settings but not username. I have just tested your theory and it appears correct that for some reason on *both* our win32 servers, ident isnt resolving for any users. Why could this be? heh, they are using near identical conf files to the linux servers. |
|
|
Hmm perhaps there is a bug with ident under win32, I'll look into it. |
|
|
"username" is the part before the @ in email address. |
|
|
Several ident bugs were fixed in beta15. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-11-20 19:46 | syzop | Status | resolved => closed |
