View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004640 | unreal | ircd | public | 2016-04-05 14:16 | 2016-04-24 11:13 |
| Reporter | dboyz | Assigned To | syzop | ||
| Priority | normal | Severity | block | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.0.2 | ||||
| Summary | 0004640: Consistently use SID when sending to servers that support SID | ||||
| Description | The title says it all. This will make services and pseudo-server developers happy. I will submit a PR within a day or two. | ||||
| 3rd party modules | |||||
|
|
Not sure what this means. If you mean the initial SERVER message from the outgoing connecting server, that one has to be SERVER because you don't know yet if the other server supports SID. Or if you mean sending SID for non-SID capable servers, that's not possible, since they have no SID. Docs can be improved, though. |
|
|
No response / No PR. Does not seem like a bug. Definitely not of severity 'block' (which is highest, even higher than 'crash'). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-04-05 14:16 | dboyz | New Issue | |
| 2016-04-09 09:13 | syzop | Note Added: 0019209 | |
| 2016-04-09 09:15 | syzop | Note Edited: 0019209 | |
| 2016-04-09 09:15 | syzop | Note Edited: 0019209 | |
| 2016-04-09 09:25 | syzop | Assigned To | => syzop |
| 2016-04-09 09:25 | syzop | Status | new => feedback |
| 2016-04-24 11:13 | syzop | Note Added: 0019240 | |
| 2016-04-24 11:13 | syzop | Status | feedback => closed |
| 2016-04-24 11:13 | syzop | Resolution | open => no change required |
