Anope IRC Services

Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1]   Go Down

Author Topic: big bug  (Read 11718 times)

0 Members and 1 Guest are viewing this topic.

Jumbo

  • Anope User
  • Offline Offline
  • Posts: 22
big bug
« on: July 01, 2007, 07:26:48 AM »

when a nickname is turned on with the mode SET IMMED, the nickname cannot be used anymore because no command is found to identify the nickname

how to solve this?

any setting to prevent services flood?

[Edited on 1-7-2007 by Jumbo]
Logged

owine

  • Anope User
  • Offline Offline
  • Posts: 130
(No subject)
« Reply #1 on: July 01, 2007, 08:10:03 AM »

Add a hostmask to the NS ACCESS list. This is a list of hostmasks that will not be killed/changed if they are using a protected nick. This will allow you to identify to the nick.
Logged

Jumbo

  • Anope User
  • Offline Offline
  • Posts: 22
(No subject)
« Reply #2 on: July 01, 2007, 09:19:34 AM »

i think the NS ACCESS list can only be edited when u r using the nickname right?

now the situation is:
- the nickname access list is empty
- the nickname is under SET KILL IMMED mode

what should i do to take back that nickname??
i thought that it should have some commands like other network services:
- /NickServ IDENTIFY <password>
or
- /NickServ IDENTIFY <nickname> <password>

how come the user need to reidentify thir nickname while changing within the same session?

=(

any is there any setting to detect and kill those are are flooding services?

[Edited on 1-7-2007 by Jumbo]
Logged

Jan Milants

  • Team
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 1372
(No subject)
« Reply #3 on: July 01, 2007, 11:02:57 AM »

Quote
what should i do to take back that nickname??

group another nickname to the other nick, that way you can change to the lost nick, change access list and then drop the newly regged nick.

and the NSAddAccessOnReg directive in the configuration file would have prevented your problem...


Quote
how come the user need to re-identify their nickname while changing within the same session?

because you didn't bother reading the entire services.conf....
Quote
# NSNickTracking  [OPTIONAL]
#
# When enabled, services will track your last nick identified when issuing
# nick changes.

#NSNickTracking


as for flooding the services, if you correctly configure your ircd's Y-lines (class blocks) clients attempting to flood should be kicked off the network long before services get into any problems...
Logged
If you like me donate coins to 1FBmZVT4J8WAUMHKqpWhgNVj3XXnRN1cCk :)

Jumbo

  • Anope User
  • Offline Offline
  • Posts: 22
(No subject)
« Reply #4 on: July 01, 2007, 11:55:46 AM »

awww... -,-"
i dont really understand what it means >,<
so i changed few settings in the config, my new problem again
in default, botserv deop me when i join a botserv-stationed channel
now it wont deop anymore, wad is the setting? i thought it should be UlineServers  but im wrong |:(
Logged

Jobe

  • Contributor
  • *
  • Offline Offline
  • Gender: Male
  • Posts: 1023
    • Anope IRC Services
(No subject)
« Reply #5 on: July 01, 2007, 12:19:25 PM »

Probably me being pedantic, but not being able to use a kill immed nick is expected behaviour :D

You can of course use /msg NickServ saset kill off to turn the kill protection off, allowing you to use the nick to add a mask to the access list.
Logged
Your IP: ()
My IRC Status:

Come along and visit http://www.anopequotes.org/

Jumbo

  • Anope User
  • Offline Offline
  • Posts: 22
(No subject)
« Reply #6 on: July 01, 2007, 12:31:31 PM »

WHEE I LOVE U ABOUT THE NS COMMAND

btw...

Quote
...
so i changed few settings in the config, my new problem again
in default, botserv deop me when i join a botserv-stationed channel
now it wont deop anymore, wad is the setting?
...
Logged

katsklaw

  • Guest
(No subject)
« Reply #7 on: July 01, 2007, 12:58:11 PM »

so to be clear this is not a bug, but 2 features that are working properly as intended that happen to conflict with your desires.

In short, don't use kill immed with an empty ns access list.
Logged

Jumbo

  • Anope User
  • Offline Offline
  • Posts: 22
(No subject)
« Reply #8 on: July 01, 2007, 01:47:05 PM »

by posting this i just wanted to repeat another question of mine in my few posts before this

default, services deop me when i join an empty registered channel
after i changed a few settings in services.conf
the services not deop me when i join an empty registered channel anymore

conclusion: services wont deop a person who joined an empty-registered channel
anyone know what is the problem?

[Edited on 1-7-2007 by Jumbo]
Logged

chlspvh18

  • Anope User
  • Offline Offline
  • Gender: Male
  • Posts: 25
(No subject)
« Reply #9 on: July 01, 2007, 10:41:24 PM »

I'll give a sugestion
REGAIN command could be very useful
but we don't have this command in anope (maybe a module could help =P)

You use /Nickserv REGAIN nickname password
and you change your nickname and identify it at the same time
it's like a "3 in 1" command:

-You change your nickname
-You identify it
-And if there's a "ghost" IRC session or another person using your nickname, it will be killed.

So, it's possible to use your nickname when KILL IMMED is activated

i hope you understand what i'm trying to say =P

Jumbo

  • Anope User
  • Offline Offline
  • Posts: 22
(No subject)
« Reply #10 on: July 01, 2007, 10:57:27 PM »

i would happy if you can tell me how to do or where can i download such modules and how do i run it

but that is not the problem that i am facing now

Quote
services wont deop a person who joined an empty-registered channel
Logged

katsklaw

  • Guest
(No subject)
« Reply #11 on: July 01, 2007, 11:49:15 PM »

Quote
Originally posted by chlspvh18
I'll give a sugestion
REGAIN command could be very useful
but we don't have this command in anope (maybe a module could help =P)

You use /Nickserv REGAIN nickname password
and you change your nickname and identify it at the same time
it's like a "3 in 1" command:

-You change your nickname
-You identify it
-And if there's a "ghost" IRC session or another person using your nickname, it will be killed.

So, it's possible to use your nickname when KILL IMMED is activated

i hope you understand what i'm trying to say =P


It's always been possible to use kill immed is active, you just can't do it with an empty access list is all ..

[Edited on 1-7-2007 by katsklaw]
Logged

Jumbo

  • Anope User
  • Offline Offline
  • Posts: 22
(No subject)
« Reply #12 on: July 02, 2007, 06:05:27 AM »

okok, lets forget about the nickname that i am talking about previosly

lets come to this
services wont deop a person who joined an empty-registered channel
what is the problem?
Logged

chlspvh18

  • Anope User
  • Offline Offline
  • Gender: Male
  • Posts: 25
(No subject)
« Reply #13 on: July 03, 2007, 09:11:52 PM »

yeah katsklaw
but this command would be useful if you're trying to use your nickname
from a address that is not on your access list or if access list is empty.
and i think it's more practical you use REGAIN than /NickServ GHOST nickname password and /Nick yournickname if your computer crashes or your internet or modem connection goes down
It's a suggestion for modules developers =P
The command that Jumbo said "/NickServ IDENTIFY <nickname> <password>"
could be useful too.

katsklaw

  • Guest
(No subject)
« Reply #14 on: July 03, 2007, 09:53:29 PM »

it's more practical, and less of a headache on opers, to not use kill immed to start with. It's not going to hurt anyone if someone uses their nick for 20 seconds. and that 20 seconds give you more than enough time to identify when using a host other than one on your access list. See? .. problem solved without coding yet another command that prevents something that didn't need to be prevented in the first place.

As far as REGAIN vs GHOST, there is nothing more practical about it.. it's just a word "regain" or "ghost" they would function 100 % identical. Not to mention that ghost isn't used if Services is enforcing your nick, you need to use recover or release, which also do the exact same thing that ghost does and in the future I'm sure ghost, release and recover will all be the same command. Adding regain to that list of redundancy would only be .. well, ... redundant.

I do agree that Anope needs to support remote identification, that point has been debated on many occasions and it may appear in 1.9 or it may not ..

[Edited on 3-7-2007 by katsklaw]
Logged

chlspvh18

  • Anope User
  • Offline Offline
  • Gender: Male
  • Posts: 25
(No subject)
« Reply #15 on: July 03, 2007, 11:35:38 PM »

yeah
i thought it could be useful and solve this problem with kill immed.
in brasnet, my nickname always had KILL IMMED on
and access list empty, and i always used REGAIN command to get my nick =P

[Editado em 3/7/2007 por chlspvh18]

katsklaw

  • Guest
(No subject)
« Reply #16 on: July 04, 2007, 12:30:40 AM »

Quote
Originally posted by chlspvh18
yeah
i thought it could be useful and solve this problem with kill immed.
in brasnet, my nickname always had KILL IMMED on
and access list empty, and i always used REGAIN command to get my nick =P

[Editado em 3/7/2007 por chlspvh18]


You could use the OLD ns_ghost module found on the old modules site .. edit it and change the command name to regain and use that.
Logged
Pages: [1]   Go Up