View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004893 | unreal | ircd | public | 2017-03-11 22:46 | 2017-03-13 19:08 |
| Reporter | Eman | Assigned To | syzop | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | unable to duplicate | ||
| Product Version | 4.0.10 | ||||
| Summary | 0004893: joins passing +D | ||||
| Description | <Jobe> so the bug with +D is that some messages that match spamfilters still result in a JOIN being sent, even though the user no longer exists | ||||
| Additional Information | please contact Jobe for more info. | ||||
| 3rd party modules | |||||
|
|
I cannot reproduce this. Both with a spamfilter that kills and and also not with a spamfilter that blocks. Jobe has ops in #unreal-support. Ops see joins as usual (as if +D has no effect). Is he sure it isn't just that? |
|
|
I had a second user logged in in #unreal-support during a bot flood the other night. Several bots that triggered a spamfilter resulted in a JOIN message being sent to the second non-opped user despite the source of the JOIN having already been disconnected. Where this occurred the server notice that notified me of the spamfilter match appeared as: * [Spamfilter] Eboj!~Jobe@<removed> matches filter '*fags*': [PRIVMSG #unreal-support: ' Which as you can see is incomplete compared with how it should show: * [Spamfilter] Eboj!~Jobe@<removed> matches filter '*fags*': [PRIVMSG #unreal-support: 'fags'] [Please stop messing around] So whatever caused it may also have caused messages to be truncated too. |
|
|
Forgot to also mention that because the user the JOIN was for had already been disconnected it resulted in the second non-opped user's nick list populating with non-existent users. It got up to a total of 85 users while the channel only had 70 users total. |
|
|
So from logs I have available it appears it was my client truncating the spamfilter notices. |
|
|
Was a strange issue. Any join on irc2.unrealircd.org was not 'hidden', while it should be. Both ircds were running 4.0.10-rc2. After upgrading both irc2 and irc1 to latest version I (or 'we', this is still unclear) could no longer reproduce the issue. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-03-11 22:46 | Eman | New Issue | |
| 2017-03-13 08:43 | syzop | Note Added: 0019689 | |
| 2017-03-13 12:28 | syzop | View Status | private => public |
| 2017-03-13 13:06 | Jobe | Note Added: 0019690 | |
| 2017-03-13 13:07 | Jobe | Note Added: 0019691 | |
| 2017-03-13 13:44 | Jobe | Note Added: 0019692 | |
| 2017-03-13 19:08 | syzop | Assigned To | => syzop |
| 2017-03-13 19:08 | syzop | Status | new => closed |
| 2017-03-13 19:08 | syzop | Resolution | open => unable to duplicate |
| 2017-03-13 19:08 | syzop | Note Added: 0019693 | |
| 2017-03-13 19:08 | syzop | Note Edited: 0019693 |
