Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: Small AddAkiller Modification  (Read 4055 times)

0 Members and 1 Guest are viewing this topic.

User123

  • Guest
Small AddAkiller Modification
« on: January 02, 2007, 03:11:55 AM »

Just wondering if it's possible to change the AddAkiller option to make it add the operator's nickname they have access under to the Akill reason instead of their current nickname in use?

Having it this way makes it show the operator's 'main' nickname in Akill reasons everytime instead of other nicknames such as if the nickname was unregistered or having a variety of different nicknames which are not on the staff list.

This is also good from both a user and oper point-of-view as you know who exactly set the ban when it gets triggered instead of seeing [Not^Here]
Logged

katsklaw

  • Guest
(No subject)
« Reply #1 on: January 02, 2007, 04:26:51 AM »

Quote
Originally posted by User123
Just wondering if it's possible to change the AddAkiller option to make it add the operator's nickname they have access under to the Akill reason instead of their current nickname in use?


a quick /ns glist nick will tell you what the main group nick is.

Code: [Select]

.::23.12::. -NickServ- List of nicknames in the group of katsklaw:
.::23.12::. -NickServ-     katsklaw (expires in Jan 31 22:43:19 2007 EST)
.::23.12::. -NickServ-     kats-AFK (expires in Jan 19 19:22:11 2007 EST)
.::23.12::. -NickServ- 2 nicknames in the group.


Quote

Having it this way makes it show the operator's 'main' nickname in Akill reasons everytime instead of other nicknames such as if the nickname was unregistered or having a variety of different nicknames which are not on the staff list.


Unregistered nicks cannot use /os commands, so all nicks will be registered and will either be the main nick or in a group. Even if OSOpersOnly is disabled, you still have to be identified to a registered nick on Services access list to gain access to OperServ commands.

Quote

This is also good from both a user and oper point-of-view as you know who exactly set the ban when it gets triggered instead of seeing [Not^Here]


What if the opers nick is [Not^Here] ?? You should see what nick was used when the akill was placed in case somehow an unauthorised user got placed in a group they aren't supposed to be in. If you use the main group nick then it's alot harder to find who actually set the akill.

So in short it's alot easier to do /ns glist nick than to scour a weeks worth of logfiles finding out who actually set the akill in the event an account was somehow hijacked.
Logged

Jobe

  • Contributor
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 1023
    • Anope IRC Services
(No subject)
« Reply #2 on: January 02, 2007, 10:46:24 AM »

Also if you use an IRCd that supports /whowas knowing the main nick of the person who set an AKILL wont help where as knowing the nick used at the time to set the AKILL WILL help. SInce you can simply do /whowas NICK to see what hosts have used that nick.
Logged
Your IP: ()
My IRC Status:

Come along and visit http://www.anopequotes.org/
Pages: [1]   Go Up