Hola,
Apologies if i'm being terribly unobservant, but searching the manual, faq and forums returned nothing on this.
Is there any way to limit nick lengths?
Ta.
Nick Limits
Of course there is! however we at Unreal do not support modifying of any kind.
http://www.vulnscan.org/UnrealIrcd/faq/#40
http://www.vulnscan.org/UnrealIrcd/faq/#40
FBSD-DEV Project
http://www.fbsd-dev.org
YatesDev Hosting
http://www.yatesdev.com
The Wrong Way
http://www.thewrongway.net
http://www.fbsd-dev.org
YatesDev Hosting
http://www.yatesdev.com
The Wrong Way
http://www.thewrongway.net
Most likely the question was more than a simple "is there", maybe he wants to know what those ways are if they exist.
Of course the easiest way is to alter the ircd source, however that isn't supported, as others said. There are no better ones thought.
I don't know what your problem is with the current limitation that allows max. 30 characters in a nickname, but if that number is too high for you, I can show you a not very smart but effective way, and it doesn't even require you to modify the ircd source. Here's an example:
The only disadvantage of this is that it may produce tons of Q:Line notices on a big network.
Therefore you might want to get rid of the 'q' snomask.
Of course the easiest way is to alter the ircd source, however that isn't supported, as others said. There are no better ones thought.
I don't know what your problem is with the current limitation that allows max. 30 characters in a nickname, but if that number is too high for you, I can show you a not very smart but effective way, and it doesn't even require you to modify the ircd source. Here's an example:
Code: Select all
ban nick
{
mask "?????*";
reason "Nicknames are not allowed to be more than 5 characters long.";
};-
codemastr
- Former UnrealIRCd head coder
- Posts: 811
- Joined: Sat Mar 06, 2004 8:47 pm
- Location: United States
- Contact:
Interesting idea using a ban nick...
TKL + Q H ?????* <nickname of setter> 0 <epoch time set at> :<reason>
The H indicates that it is a hold. When you add a hold, no Q:line notices are generated.
You can work around that in 3.2 final. It introduced a new qline called a "hold." It is set by services with the TKL command. Basically it does:The only disadvantage of this is that it may produce tons of Q:Line notices on a big network. Therefore you might want to get rid of the 'q' snomask.
TKL + Q H ?????* <nickname of setter> 0 <epoch time set at> :<reason>
The H indicates that it is a hold. When you add a hold, no Q:line notices are generated.
-- codemastr
@aquanight: At first I thought the same, but after trying what ?????* does, I realized, it doesn't work the way we would expect:
@codemastr: Thanks for the idea, it's quite useful. :)*irc*> stats bannick
217 q:?????*:0:1088246723:server1.test.com:Nicknames
219 q : End of /STATS report
*irc*> nick abcde
*** test is now known as abcde
*irc*> nick abcdef
432 abcdef : Erroneous Nickname: Nicknames are not allowed to be more than 5 characters long.