View Issue Details

IDProjectCategoryView StatusLast Update
0004083unrealircdpublic2012-08-17 13:13
Reporterkatsklaw Assigned To 
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionno change required 
Product Version3.2.9 
Summary0004083: IsRegNick doesn't honor user->svid as an authenticated user
DescriptionIsRegNick is used by umode +R and cmodes +R +M to check for umode +r. However, since ESVID was added, IsRegNick still only checks for UMODE_REGNICK only.

This will break the above mentioned modes if services uses svid without sending umode +r as well.
3rd party modules

Activities

katsklaw

2012-02-03 02:14

reporter   ~0016901

Actually this may not be an issue because both Atheme and Anope at least send mode +rd.

However, I think it silly to have both "is a registered user" and "is logged in as" in the /whois. Do we really need to set both?

syzop

2012-02-26 21:38

administrator   ~0016922

As you already commented, services have to send +r when a user is registered.
SVID is only an enhancement to replace the current servicestamp, nothing more.

As for your 2nd comment, yes the SVID field is shown in /WHOIS if it's known.
I don't think the 'is registered' message should go, that would mean for some services packages you would have such a message, while for others you would have the 'logged in as' message (and numeric). That sounds confusing?
I don't know what other ircds do?

nenolod

2012-02-28 06:26

reporter   ~0016934

Last edited: 2012-02-28 06:27

The baseline recommendation for legacy IRCd software which has had a registered usermode is to continue to support the registered usermode and send +r/-r when the account is authenticated *and* on an owned nick.

If the account is authenticated, but the nickname is not owned by that account, then only the accountname should be sent in WHOIS. This is the current behaviour of Atheme -- I do not know what Anope's behaviour is.

katsklaw

2012-03-06 04:09

reporter   ~0016938

ok, so this is likely a squabble over nothing. Thanks

Issue History

Date Modified Username Field Change
2012-02-03 02:06 katsklaw New Issue
2012-02-03 02:14 katsklaw Note Added: 0016901
2012-02-26 21:38 syzop Note Added: 0016922
2012-02-26 21:38 syzop Priority high => normal
2012-02-26 21:38 syzop Status new => feedback
2012-02-28 06:26 nenolod Note Added: 0016934
2012-02-28 06:27 nenolod Note Edited: 0016934
2012-03-06 04:09 katsklaw Note Added: 0016938
2012-08-17 13:13 syzop Status feedback => closed
2012-08-17 13:13 syzop Resolution open => no change required