Release notes for ircu2.10.12
-Last updated: 14 Jan 2005
+Last updated: 1 Sep 2005
Written by Michael Poole <mdpoole@troilus.org>
Based on earlier documents by Kev <klmitch@mit.edu> and
Braden <dbtem@yahoo.com>.
This document briefly describes changes in ircu2.10.12 relative to
ircu2.10.11. ircu2.10.12 is only compatible with servers that
implement the P10 protocol. It has been tested to link against
-ircu2.10.11, but some features (notably IPv6 support) are not
-supported by ircu2.10.11.
+ircu2.10.11, but some features (notably IPv6 support and oplevels) are
+not supported by ircu2.10.11.
+
+Semantic Changes (TAKE NOTE):
+
+Channel keys and passwords (see the "oplevels" enhancement below)
+listed in a JOIN are now only checked against the corresponding
+channel. In ircu2.10.11, "JOIN #a,#b key" would attempt to use "key"
+as the key for both #a and #b. ircu2.10.12 will only attempt to use
+it as the key for #a. ircu2.10.12's behavior matches that documented
+in RFC 1459.
Enhancements:
when you join using those keys. Part of this channel protection is
that you cannot be deopped in channel by someone who you opped.
+A new channel mode, +D, has been added for auditorium-style channels.
+These are channels where most users listen but do not speak or receive
+ops or voice. The effect of +D is that the server waits to send the
+JOIN message for new users until the user gets ops or voice or sends a
+message to the channel. A list of join-delayed users in a channel may
+be retrieved by using /NAMES -d #channel. The response to /NAMES -d
+uses the same format as numeric 353, but uses numeric 355 instead. If
+an op removes +D while there are still join-delayed users, the server
+automatically sets mode +d, and removes +d when the last user's join
+is shown. It is not possible to set channel mode +d manually; its
+purpose is to warn channel users that there are "hidden" users in the
+channel.
+
More than one hashing mechanism is now supported for oper passwords,
and a new tool (ircd/umkpasswd) is provided to generate them.
commands like /X or /CHANSERV from their client, without tying the
admin to a particular arrangement or naming of services.
-Clients may negotiate extensions and changes to the standard IRC
-client protocol by using the CAP command during registration. There
-does not appear to be any documentation for the protocol, which should
-not matter since ircu does not currently implement capabilities that
-affect the protocol.
-
The /stats command accepts string identifiers in addition to
single-character identifiers. For example, "/stats access" shows the
same data as "/stats i". Supported names are shown by /stats. New
Client blocks (previously I: lines), Operator blocks (previously O:
and o: lines), channel bans and silences may use CIDR notation instead
of simple wildcards. You may also have silence exceptions by putting
-'-' before the mask; for example, if you wish to silence everyone
-except X, you could use SILENCE *!*@*,-X!cservice@undernet.org.
+'~' before the mask; for example, if you wish to silence everyone
+except X, you could use SILENCE *!*@*,~X!cservice@undernet.org.
The server will no longer kick "net riders" in keyed (+k) channels if
both sides of the net join have the same key.
+IP masks (as used in bans, G-lines, etc) are now parsed in a more
+forgiving manner. 127.0.0.0/8, 127.* and 127/8 are all accepted and
+mean the same thing. Ambiguous expressions like 127/8 are interpreted
+as IPv4 masks; to interpret it as an IPv6 mask, use 127:/8.
+
Configuration Changes:
As mentioned above, the configuration file format has changed
Deleted features since they are now controlled by other configuration
entries: VIRTUAL_HOST, oper and locop privilege features.
+Deleted feature since it no longer applies: HIS_STATS_h.
+
Compile Time Options:
A listing of supported compile-time options may be seen by running
projects / ircu2.10.12-pk.git / blobdiff