Anope Bug Tracker - Anope Development (1.9.x series)
View Issue Details
0001459Anope Development (1.9.x series)Chanservpublic2012-11-02 20:082012-11-10 02:24
Raphael 
Adam 
normalminoralways
resolvedfixed 
64xLinuxUbuntu 12.10
 
 
0001459: ChanServ Access ADD/LIST/DEL adding hostname
To add:
/chanserv access #xatneorotico add maay_lock 3
Show:
(13:53:21) -ChanServ- *!*@7fa4k5.telesp.net.br adicionado r lista de acesso do #xatneorotico com o nível 3.



To list:
(13:52:31) -ChanServ- Access list for #xatneorotico:
(13:52:31) -ChanServ- Number Level Mask
(13:52:31) -ChanServ- 1 9999 mc-alex
(13:52:31) -ChanServ- 2 3 *!*@38t.8j5.102.177.IP
(13:52:31) -ChanServ- 3 3 *!*@4u0daj.veloxzone.com.br
(13:52:31) -ChanServ- 4 3 *!*@lq7.l3a.166.200.IP
(13:52:31) -ChanServ- 5 3 *!*@56k.iju.113.177.IP
(13:52:31) -ChanServ- 6 3 gustavo
(13:52:31) -ChanServ- 7 3 gustavo^^
(13:52:31) -ChanServ- 8 3 *!*@n8s3dt.veloxzone.com.br
(13:52:31) -ChanServ- 9 3 *!*@cqorc6.telesp.net.br
(13:52:31) -ChanServ- 10 3 *!*@ceq.4b7.10.201.IP
(13:52:31) -ChanServ- 11 3 *!*@7fa4k5.telesp.net.br



To remove:
/chanserv access #xatneorotico del Maay_Lock
Show:
(13:53:56) -ChanServ- maay_lock nao foi encontrado na lista de acesso do #xatneorotico. (not found)



To remove:
/chanserv access #xatneorotico del *!*@7fa4k5.telesp.net.br
Show:
(13:54:05) -ChanServ- *!*@7fa4k5.telesp.net.br removido da lista de acesso do #xatneorotico. (removed successfuly)
To add:
/chanserv access #xatneorotico add maay_lock 3
Show:
(13:53:21) -ChanServ- *!*@7fa4k5.telesp.net.br adicionado r lista de acesso do #xatneorotico com o nível 3.



To list:
(13:52:31) -ChanServ- Access list for #xatneorotico:
(13:52:31) -ChanServ- Number Level Mask
(13:52:31) -ChanServ- 1 9999 mc-alex
(13:52:31) -ChanServ- 2 3 *!*@38t.8j5.102.177.IP
(13:52:31) -ChanServ- 3 3 *!*@4u0daj.veloxzone.com.br
(13:52:31) -ChanServ- 4 3 *!*@lq7.l3a.166.200.IP
(13:52:31) -ChanServ- 5 3 *!*@56k.iju.113.177.IP
(13:52:31) -ChanServ- 6 3 gustavo
(13:52:31) -ChanServ- 7 3 gustavo^^
(13:52:31) -ChanServ- 8 3 *!*@n8s3dt.veloxzone.com.br
(13:52:31) -ChanServ- 9 3 *!*@cqorc6.telesp.net.br
(13:52:31) -ChanServ- 10 3 *!*@ceq.4b7.10.201.IP
(13:52:31) -ChanServ- 11 3 *!*@7fa4k5.telesp.net.br



To remove:
/chanserv access #xatneorotico del Maay_Lock
Show:
(13:53:56) -ChanServ- maay_lock nao foi encontrado na lista de acesso do #xatneorotico. (not found)



To remove:
/chanserv access #xatneorotico del *!*@7fa4k5.telesp.net.br
Show:
(13:54:05) -ChanServ- *!*@7fa4k5.telesp.net.br removido da lista de acesso do #xatneorotico. (removed successfuly)
Whois of Maay_Lock:
Maay_Lock is Webd95d@7fa4k5.telesp.net.br * WebChat xatneorotico.falai.org
Maay_Lock is connecting from Webd95d@201-43-xx-xx.dsl.telesp.net.br 201.43.xx.xx
Maay_Lock on +#xatneorotico
Maay_Lock using br.falai.org Powered by Falai
Maay_Lock is using modes +x
Maay_Lock End of /WHOIS list.

(13:52:56) <ChanServ> OVERRIDE: raphael!ph@189.72.230.144 used access on #xatneorotico to delete *!*@7fa4k5.telesp.net.br

(13:53:21) <ChanServ> OVERRIDE: raphael!ph@189.72.230.144 used access on #xatneorotico to add *!*@7fa4k5.telesp.net.br with level 3

(13:54:05) <ChanServ> OVERRIDE: raphael!ph@189.72.230.144 used access on #xatneorotico to delete *!*@7fa4k5.telesp.net.br
No tags attached.
Issue History
2012-11-02 20:08RaphaelNew Issue
2012-11-02 20:11RaphaelNote Added: 0006296
2012-11-06 17:31LEthaLityNote Added: 0006297
2012-11-06 17:36LEthaLityPriorityurgent => normal
2012-11-06 17:36LEthaLitySeveritymajor => minor
2012-11-06 17:36LEthaLityReproducibilitysometimes => always
2012-11-10 02:24AdamNote Added: 0006301
2012-11-10 02:24AdamStatusnew => resolved
2012-11-10 02:24AdamResolutionopen => fixed
2012-11-10 02:24AdamAssigned To => Adam

Notes
(0006301)
Adam   
2012-11-10 02:24   
I have changed access del and xop del to behave like access add/xop add now, so it will use the users hostmask.

Fixed in 8f36f65f39c6ea843c388af398ed0bbfe84d1207
(0006297)
LEthaLity   
2012-11-06 17:31   
The reason it adds a hostname is because the user isn't registered with NickServ, this is a new intentional thing that differs from 1.8. The hostmask is added to the access list as it's more secure then a nickname that anyone could /nick to.

I do think though that services could check if an online unregistered users hostmask matches one in the access list.
(0006296)
Raphael   
2012-11-02 20:11   
Description:

Sometimes using the command /chanserv access to add an user on userlist channel but the registered data is the hostname. Then when we will remove some user from the list the services don't find the user and we need to remove the user by hostname.