You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
The specification of the USER command was modified in RFC2812.
RFC1459: USER <username> <hostname> <servername> <realname>
RFC2812: USER <username> <mode> <unused> <realname>
where <mode> is an integer bitmask that can be comprised of the following bit fields:
USER_MODE_WALLOPS = 4
USER_MODE_INVISIBLE = 8
(NB. most major ircds will just ignore the mode field and set their own default usermodes on connect anyway - most clients just send 8 or 12 as an unconfigurable default value)
Only the names of the parameters, really. Since RFC2812 supersedes RFC1459, we should at least add the new parameter names, even if the old ones are kept alongside for backwards compatibility.
The USER test case strings currently use the old syntax as well - these should be changed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The specification of the
USER
command was modified in RFC2812.RFC1459:
USER <username> <hostname> <servername> <realname>
RFC2812:
USER <username> <mode> <unused> <realname>
where
<mode>
is an integer bitmask that can be comprised of the following bit fields:USER_MODE_WALLOPS
= 4USER_MODE_INVISIBLE
= 8(NB. most major ircds will just ignore the mode field and set their own default usermodes on connect anyway - most clients just send 8 or 12 as an unconfigurable default value)
ref: https://tools.ietf.org/html/rfc2812#section-3.1.3
The text was updated successfully, but these errors were encountered: