[srvx-bugs] [ srvx-Bugs-829084 ] Lacking EnfModes access can lead to mode desync

[SourceForge.net <no...@so...>]

Bugs item #829084, was opened at 2003-10-23 12:01
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=403001&aid=829084&group_id=31654

Category: ChanServ
Group: 1.2
Status: Open
Resolution: None
Priority: 5
Submitted By: Joe Hansche (joeatrr)
Assigned to: Zoot (zoot)
Summary: Lacking EnfModes access can lead to mode desync

Initial Comment:
When using !mode in a channel where the user lacks
enfmodes access, and the mode change involves at least
1 mode that violates the mode-lock, and one mode that
does not, ChanServ first alters its channel node to
reflect the mode change, then checks those modes
against the mode-lock.  Since the mode-lock was
violated, ChanServ re-sets the locked mode, and cancels
the mode propagation to the servers.  That means the
non-violating mode change was changed in srvx, but not
on the servers, which creates a mode desync.

Modes in #testmodes are +mtin.
 <@madCoder> !set modes
 <<[ChanServ]<- Modes        +i
 <@madCoder> !peek
 <<[ChanServ]<- #testmodes Status:
 <<[ChanServ]<- Topic:          
 <<[ChanServ]<- Modes:          +mtin
 <@madCoder> !mode -im
 <<[ChanServ]<- Modes conflicting with +i are not
allowed in #testmodes.
 <@madCoder> !peek
 <<[ChanServ]<- #testmodes Status:
 <<[ChanServ]<- Topic:          
 <<[ChanServ]<- Modes:          +tin

but the channel's modes are still +mtin on the server
(so the -m was done in srvx, but not propagated to the
rest of the network).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=403001&aid=829084&group_id=31654