View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001167 | unreal | ircd | public | 2003-08-03 15:35 | 2003-08-03 21:36 |
| Reporter | Praetorian_ | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta17 | ||||
| Summary | 0001167: SERVER / PASS / PROTOCTL tokens dont work in inital connection | ||||
| Description | On a server connecting to a network (services or otherwise), unreal does not seem to under if it gets ` (SERVER token) instead of SERVER, when it is introducing itself, even if TOKEN is in the PROTOCTL string. The same applies for the other keywords, PASS and PROTOCTL... see steps to reproduce for more of an idea | ||||
| Steps To Reproduce | This will work: PROTOCTL NOQUIT TOKEN NICKv2 SJOIN SJOIN2 SJ3 UMODE2 VL VHP PASS :pass SERVER server.name 1 10 :Really rad server.. This won't work: PROTOCTL NOQUIT TOKEN NICKv2 SJOIN SJOIN2 SJ3 UMODE2 VL VHP < :pass ` server.name 1 10 :Really rad server.. This won't work: PROTOCTL NOQUIT TOKEN NICKv2 SJOIN SJOIN2 SJ3 UMODE2 VL VHP PASS :pass ` server.name 1 10 :Really rad server.. any of them basically with a tokenised keyword wont work.. | ||||
| 3rd party modules | |||||
|
|
The initial registration must not be done using tokens. Thats not a bug, thats how it is designed. In fact the initial registration should NOT use any protoctl. It can only lead to problems. |
|
|
It won't accept tokens if the server isn't authorized yet (PASS+SERVER), this is the correct behavior IMHO. |
|
|
ok no probs then. was just curious :) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-08-03 15:35 | Praetorian_ | New Issue | |
| 2003-08-03 18:08 |
|
Note Added: 0003399 | |
| 2003-08-03 18:09 | syzop | Note Added: 0003400 | |
| 2003-08-03 21:22 | Praetorian_ | Note Added: 0003401 | |
| 2003-08-03 21:36 | syzop | Status | new => closed |
