Age | Commit message (Collapse) | Author |
|
|
|
This is not something the average user will encounter. It can only
happen if the user sends a message with preceding whitespace or a
prefix but no command name.
This is not something that should ever be seen in practise so we
just penalise the user and pretend nothing ever happened.
The previous code also contained undefined behaviour but it acted
sensibly on all compilers we support so it was not crashable.
|
|
We always send "Connection: Close" so this is the right behaviour
according to section 8.1 of RFC 2616.
Closes #1507.
|
|
|
|
|
|
|
|
|
|
Closes #1503.
|
|
Thanks to @SleepyEntropy for pointing out that multiple internet-
accessible servers do not have these modules correctly configured.
|
|
|
|
|
|
* Improve exemptchanops in inspircd.conf.example (<options>)
and modules.conf.example; along with both helpop examples.
* Add "the" to all "requires X module" in both helpop examples.
* Refer to customprefix instead of chanprotect and halfop.
* Add SNOMASK 'r' and 'R' (OPERLOG) to both helpop examples.
* Clean up unnecessarily split SNOMASK lines in both helpop examples.
* Move chmode 'g' to be in alphabetical order in both helpops examples.
* Specify the needed mask formats for TLINE in helpop-full example.
* Remove extra '\' in RLINE mask format in helpop-full example.
Force xml format in helpop-full
* Generalize "color codes" to "formatting codes"
* Fix file name in include for example helpop-full
|
|
|
|
|
|
Closes #1240.
|
|
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.
|
|
ChangeIP() calls SetClientIP() which revalidates whether the user
matches an ELine. However, because the hostname has not changed yet
the user may incorrectly be marked as non-exempt.
|
|
Since CGI:IRC calls it's 'ChangeIP()' either from 'OnCheckReady()'
or 'OnUserRegister()', both of which are called after the user has
sent NICK/USER, we can safely skip re-setting the ExtItem prior to
this point.
This skips the first 'OnSetUserIP()' from 'User::AddUser()' as
the 'OnSetConnectClass()' catch handles the initial setting.
|
|
m_ssl_openssl: Remove deprecated API members.
|
|
Backported from 2afc1af4639ae2bbef397f4f6acc834950017d91.
|
|
[2.0] Make sure banredirect metadata can not be duplicated
|
|
[2.0]: Helpop: Move extban 'U' from acting to matching
|
|
Already fixed in master in 8587df2
|
|
as requested by @Adam-
|
|
|
|
|
|
Sending history to some bots can cause problems as without the
IRCv3 chathistory batch they have no way of knowing what messages
are history and what they should respond to.
Closes #1450.
|
|
Fix two minor docs issues
|
|
|
|
This is used by modules like m_sasl to send the cgiirc hostname to
services so it should contain something valid.
Closes #1438.
|
|
|
|
|
|
|
|
|
|
As far as I can tell this is not a problem as all ban masks are
canonicalised but its better to be safe than sorry.
|
|
Fix referring to sqloper and sqlauth as extras in modules.conf.example.
|
|
|
|
|
|
This fixes installing extras modules such as m_qrcode which contain
characters from outside of the Unicode Basic Multilingual Plane.
|
|
- Remind admins that not setting a DIE/RESTART password does not
disable use of those commands.
- Remove references to 1.2 and modules being able to create custom
logging methods. This was never implemented in the 2.0 branch.
- Remove references to an SASL improvement that was reverted.
- Update various InspIRCd website links to use HTTPS over HTTP.
- Update a link to the IRCv3 website to point to the new website.
|
|
|
|
This is causing problems such as duplicate 904 messages.
|
|
2.0: Fix various inconsistencies in m_timedbans.
|
|
* Send to remote servers upon setting
* Send to halfop if available upon expiry
|
|
2.0: Inform the client when a SASL message cannot be sent
|
|
When SASL is properly configured with a 'target' server, we are able
to inform the client when the message fails to send.
Currently if a target is configured and it is offline, no response is
sent. This can cause some clients to time out while waiting for a response.
If a target isn't configured, behaviour will not change with this commit.
The default of '*' will still send to all servers.
Updated example config with 'target' variable.
|
|
This was done to the string variant in d3b82b2f7f.
|
|
Fix CMD_RESTART with relative paths as argv[0].
|
|
|
|
See: 66f82ccf926aac39273bfc652c85c08080cc9a46
Fixes inspircd/inspircd-extras#110
|