illegal character in source nick for svsnick?

The UnrealIRCd team does not officially provide support for any services packages that you may be using or want to use. This forum is provided so the community can help each other with services issues.

Moderator: Supporters

Locked
ZvOO
Posts: 7
Joined: Mon Feb 06, 2006 7:12 pm

illegal character in source nick for svsnick?

Post by ZvOO »

I'm NetAdmin on an Unreal 3.2.5/anope 1.7.15 network and I'd like to know why I can't use the OperServ svsnick function to change a nickname that contains certain characters. For example, someone changed his nick to ProCon` (ProCon is the name of one of our services bots). I first warned him to change his nick, then when he failed to do so I enabled SuperAdmin and issued:
/os svsnick ProCon` Xalt500
The response from OperServ that I get is:
[09:38] -OperServ- Nick ProCon` is an illegal nickname and cannot be used.
I realize that I'm doing this through anope services and this forum is not intended to support any services packages. But because I believe it's calling the svsnick function within the IRCd, I thought maybe someone would know why it does this. And please note that the /os svsnick command works fine on regular alphanumeric nicknames.

Thanks in advance for any reply.
Mark
Posts: 57
Joined: Mon Dec 26, 2005 4:01 pm

Post by Mark »

[31/08/06 - 19:58:49] -OperServ- You are now a SuperAdmin
[31/08/06 - 19:58:49] -SERVER.tld- *** Global -- from OperServ: Mark is now a Super-Admin
[31/08/06 - 19:58:49] -OperServ- The nick ProCon` is now being changed to Xalt500.
[31/08/06 - 19:58:49] -SERVER.tld- *** Global -- from OperServ: Mark used SVSNICK to change ProCon` to Xalt500
[31/08/06 - 19:58:49] -OperServ- You are no longer a SuperAdmin
[31/08/06 - 19:58:49] -SERVER.tld- *** Global -- from OperServ: Mark is no longer a Super-Admin
Works here? Running Anope 1.7.10.
Last edited by Mark on Fri Sep 01, 2006 7:17 am, edited 1 time in total.
ZvOO
Posts: 7
Joined: Mon Feb 06, 2006 7:12 pm

Post by ZvOO »

Works here? Running Anope 1.7.10.
That's just weird. It's hard to imagine that it's something to do with the anope version.
Stealth
Head of Support
Posts: 2086
Joined: Tue Jun 15, 2004 8:50 pm
Location: Chino Hills, CA, US
Contact:

Post by Stealth »

Moved -> Services
White_Magic
Posts: 267
Joined: Tue Jan 18, 2005 3:24 pm
Location: Scotland - United Kingdom

Post by White_Magic »

looks like a bug in Anope...

thou, ur not issuing a timestamp with the svsnick command so as a result the command would fail, the error msg ur getting i think would be becuz anope Qlines all the bot nicknames for services bots, its thinking that also the guys nickname is illegal when its not and the ircd is allowing it.

/msg operserv RAW :operserv SVSNICK nickname1 nickname2 timestamp

so an exmaple would be:
/msg operserv RAW :operserv SVSNICK White_Magic Whitey 0
i spend 4 hrs a day gaming and 14hrs on irc, for 5days a week, im not an addict :D
Jobe
Official supporter
Posts: 1180
Joined: Wed May 03, 2006 7:09 pm
Location: United Kingdom

Post by Jobe »

The OperServ SVSNICK command in Anope does not require nor expect a timestamp when sent from the client:
[16:49:53] -OperServ- Syntax: SVSNICK nick newnick
[16:49:53] -OperServ-
[16:49:53] -OperServ- Forcefully changes a user's nickname from nick to newnick.
[16:49:53] -OperServ-
[16:49:53] -OperServ- Limited to Super admins
The SVSNICK in Server to Server communications on the other hand requires a timestamp.

As for the QLine suggestion Anope SQlines the nick without wildcards so only exact matches matter and would affect the situation.

One sollution you could try is to set up an OperServ SQLine manually on the nick mask *ProCon* Eg.
/msg OperServ SQLINE ADD +0 *ProCon* Restricted Nick
White_Magic
Posts: 267
Joined: Tue Jan 18, 2005 3:24 pm
Location: Scotland - United Kingdom

Post by White_Magic »

this is indeed a anope only problem, i am running 3.2.5 and 1.7.15 and i cant reproduce it.

(Anope-1.7.15 (1128))
(Your host is *.net, running version Unreal3.2.5)

*** Permanent Global Q:line added for Procon on Sat Sep 2 16:12:29 2006 GMT (from Services.*.net: Reserved for services)
[17:12:10] -> *Opsv* RAW :opsv SVSNICK procon` bleh 0
[17:12:10] * Procon` is now known as bleh

sure i used a server<->server command since we dont allow superadmins but that maybe the bug, it wont work for superadmins directly to operserv while thru server<->server its fine
i spend 4 hrs a day gaming and 14hrs on irc, for 5days a week, im not an addict :D
Jobe
Official supporter
Posts: 1180
Joined: Wed May 03, 2006 7:09 pm
Location: United Kingdom

Post by Jobe »

Use of the OperServ RAW command in Anope is not supported and any damage caused by its use is your responsibility.

:)

Also i cannot reproduce this problem at all with Anope 1.7.15 and Unreal 3.2.5.:
[17:38:14] -bravo.invictachat.co.uk- *** Permanent Global Q:line added for ProCon on Sat Sep 02 16:38:15 2006 GMT (from services.invictachat.co.uk: Reserved for services)
[17:38:14] -BotServ- ProCon![email protected] (LOL) added to the bot list.
[17:38:31] -bravo.invictachat.co.uk- *** Notice -- Client connecting on port 6697: ProCon` ([email protected]) [clients] [secure AES256-SHA]
[17:38:38] -OperServ- You are now a SuperAdmin
[17:38:39] -bravo.invictachat.co.uk- *** Global -- from OperServ: Eboj is now a Super-Admin
[17:40:54] -OperServ- The nick ProCon` is now being changed to Xalt500.
[17:40:54] -bravo.invictachat.co.uk- *** Global -- from OperServ: Eboj used SVSNICK to change ProCon` to Xalt500
Locked