View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006457 | unreal | ircd | public | 2024-08-22 02:19 | 2024-08-22 02:19 |
| Reporter | Koragg | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 6.1.6 | ||||
| Summary | 0006457: IRCv3 ACCOUNT (account-notify) numeric is NOT sent to one's own client when it is logging into its account. | ||||
| Description | Whenever a user logs into their own account, account-notify is not sending the ACCOUNT raw for the client. This only occurs if another/second client logs into one's account. This is most likely caused by UnrealIRCd implementing account-notify before one errata, stating the following: 'A previous version of this specification didn’t make it clear that account-notify messages are sent for a client’s own account name changes.' (source: https://ircv3.net/specs/extensions/account-notify#errata) | ||||
| Steps To Reproduce | 1. Connect two clients, A and B, to the same network, and have them both join the same channel. Both must also be able to view raw/debug traffic. A services (NickServ) account is also mandatory. 2. Have client A log into the account, e.g. 'Account', and observe how only client B receives an ACCOUNT raw about this event. 3. Have client B log into the account, again 'Account' and observe how only client A receives an ACCOUNT raw for this event. Expected behavior is that clients should always receive an ACCOUNT raw, even when they themselves log into an account. | ||||
| Additional Information | This behavior should be extended to the connection registration as well (e.g. authing via SASL), as other IRCd's with plenty of IRCv3 support handle it this way as well (e.g. InspIRCd 3 does this). Additionally, if the client aughts post-connection (e.g. SASL reauth after services return, when being down during connection, or a classic /ns identify is sent), the client should also receive an ACCOUNT raw if it is on no channel, as information regarding the client itself should always be seen be seen by it (assuming this information is not oper-only, which ACCOUNT is not). | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-22 02:19 | Koragg | New Issue |
