| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
This fixes an issue with the previous commit where if a user had a
non-killing X-line applied to them (e.g. Q-line) they would not
have any further X-lines applied to them.
Thanks to @linuxdaemon for pointing this out.
|
| | |
|
| |
|
|
|
|
|
| |
When DefaultApply() adds a hit to the BanCache it uses the X-line
duration to set a duration on the entry. This can result in an
entry lasting longer than the X-line itself. Fix this by setting
the entry duration to the time left on the X-line.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Show the reason in manual xline removal SNOTICEs, just like
expiry SNOTICEs do.
This modifies XLineManager::DelLine() to require another string
reference passed to it.
Requested by @Robby-.
|
| |
|
|
|
|
|
|
|
|
| |
- Change any "-Line", ":Line", or "*line" to "-line" throughout
the X-line code, comments, and documentation.
- Add periods to the end of some notices.
- Correct a typo in the Q-line code comments.
- Update the filter module documentation (shun addition).
Co-authored-by: Robby <robby@chatbelgie.be>
|
| | |
|
| | |
|
| |
|
|
| |
Closes #1427.
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When checking for an E-Line match, we want to actually check for a
current match even if we previously matched and are set exempt.
This fixes situations where you have an E-Lined CGI:IRC address,
a G-Lined IP range for some area/host/etc and a smaller E-Lined
IP range for known good clients. Currently when CGI:IRC changes
the IP, E-Lines are rechecked but because the user is already exempt
(from the CGI:IRC E-Line), they are set no longer exempt and match
a G-Line, when they should match an E-Line.
This exact change has been done before in commit 'c8b344e' and shortly
reverted in 'c490a90' to fix issue #989 (CGI:IRC users remaining exempt
when the CGI:IRC address is E-Lined but they are not).
The actual cause to this issue was likely that the user's hostname was
not changed from the CGI:IRC hostname/IP prior to rechecking E-Lines.
This is being fixed in a separate commit.
|
| | |
| |
| |
| |
| | |
Some core code still exists in the XLine system but this will be
replaced when the XLine system is replaced later.
|
| | |
| |
| |
| | |
GCCs warnings for this are much better than Clangs.
|
| | |
| |
| |
| |
| | |
This removes the need to invalidate the cache after changing a
user's hostname.
|
| |\| |
|
| | | |
|
| | |
| |
| |
| | |
Fixes issue #989 reported by @B00mX0r
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
parameters
|
| | |
| |
| |
| | |
This is specified in RFC 1459 so we should probably use it.
|
| | | |
|
| | |
| |
| |
| | |
local_users private
|
| | | |
|
| | |
| |
| |
| | |
Change call sites to call ChangeNick()
|
| | |
| |
| |
| | |
containing it
|
| | | |
|
| | |
| |
| |
| | |
later
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
- Make operreason optional; NULL means same as quitreason
- Remove User::quietquit, it is now handled internally in spanningtree
- Send snotice about quitting remote users from spanningtree
|
| | |
| |
| |
| | |
This name is more descriptive of what is actually is used for.
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
instead of const char*
|
| | |
| |
| |
| |
| |
| | |
* 'const char*' to 'const std::string&'.
* snprintf to std::string concatenation.
* Replace duplicated OneOfMatches with InspIRCd::MatchMask.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows us to send a server notice to a user without worrying
about whether they are registered or not.
If a user receives a server notice and they are not registered
then the nickname field will contain an asterisk instead of their
nick name.
|
| | | |
|
| | |
| |
| |
| | |
BanCacheHit constructor is enough
|
| | | |
|
| |/
|
|
|
|
|
|
| |
- idle_lastmsg
- dns_done
- quitting_sendq
- exempt
- lastping
|
| |
|
|
|
|
|
|
|
| |
This fixes ADDLINEs not being propagated and /gline etc. failing for already existing but expired xlines
Special thanks to @JDowny (TinMan) for his detailed report and cooperation that made this fix possible
Fixes #306 reported by @TurkDesk
Fixes #379 reported by @JDowny
|
| | |
|
| |
|
|
| |
Part 2 of ba5c0db795824c3fc1ad48ce332d7bdc440cb77f
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
of removing them before checking anything
|
| | |
|