TWiki > Openflows > OpenFlows > ProjectFlows > IrcProject > IrcServices > IrcNicknameManagement	TWiki webs: Know| Main | Openflows | Plugins | Rocketktp | Sandbox | TWiki |
	Openflows . { Changes | Index | TreeIndex | Search | Create/GoTo }

All commands assume /msg nickserv is used in the irc client (or whatever your client uses to address private msgs to a 'user' on the server) before the commands listed below.

Help is available from the Nickserv for all commands, use help or help (command). (Help can be spammy - set your flood protection low - 30 lines+ over 30s+ or off in your client) to avoid triggering your client into auto-ignoring the nickserv.

Most useful commands:

• Register your nick -- Use register (password) to register your current nick in the Nickserv with a password. This automatically identify 's you with the Nickserv (see below).

• Identify with your nick -- At next login, or at any time, identify ('login') to the Nickserv - use id (password). You must be using the nick that you wish to identify as, of course. You cannot use any of the Nickserv management commands for your nick without using identify first.

• Protect your nick -- Various options allow various levels of protection of your nick:

• • access add -- This adds a hostmask of the form (userpattern)@(hostpattern) (eg: *john@*.foo.com) to the access list of your nick. (Use access list to see current hostmasks in your access list. Use access del to remove hostmasks. Of couse help access will display help.)

• • set secure -- (currently automatically set by Nickserv at registration) This secures some functions for your nick to require stronger authentication if users of your nick are not in the hostmask. Currently, on registration, Nickserv sets set automask on, which automagically adds anyone identify ing themselves to the Nickserv properly with password to the hostmask list. (set secure is not as powerful as it sounds, see set kill below.)

• • set kill on -- This gives a user 60s to change their nick away from the protected nick (this seems to be a hard-coded value in the server) when connecting or when a nick is recover 'd away from them. Their client will then prompt them for a new nick (depending on the client), but they wont be kicked from the server. The nick will then be protected by the Nickserv (for 10 min - server side setting), and must be release 'd by authorized users (with password) before they can claim it for themselves. Use set kill to see the current setting for kill.

• • set kill immed -- This will kill a user using a nick that is later recover 'd (see below) immediately, and not give him 60s. However, the user still has 60s to change nicks when connecting to the server again. (This is to keep clients from auto-reconnecting 100s of times a minute with the wrong nick still set and hammering the server.) However, after the 60s, if the user does not change his nick to something else, he is killed from the server again. The nick will be then protected by the nickserv as in set kill above.

• Recover your nick -- If the server hasnt already collided or killed the user (if set kill is on for your nick), then you may request a collide with recover (nick) (password). This will either kill or collide a user (kill will disconnect them, collide will give them a chance to change nicknames without disconnecting them) using the nick. Then use release (nickname) (password) to open the nick so it can be assumed by you. Obviously, you want to quickly do an id (password) to identify yourself before any annoying kiddie comes back and tries to steal it again.

• Kill ghosts -- If you get disconnected from the server, but the server hasnt timed out your connection, you will have a ghost online with your nick. Use ghost (nick) (password) to kill your ghost. This can be used to kill someone who stole your nick as well, but doesnt automatically place your nick into recover mode for protection. (If you can ghost your stolen nick, then change to it quickly, this is probably easier to use.)

Other commands available - link will allow you to associate one set of permissions/one password with multiple nicks (eg: Joe, JoeAway?, JoeLunch?, etc). See help from nickserv for help.

• setpass (nick) (newpassword) to set a new password for a user

• collide (nick) (options) Allows an operator to effectively set a recover on a nick, without needing the nick's password. Nick must be registered to use this.
  • options:
  • -list will list current collide settings
  • -set (default) Will set a nick collision for that nick to occur in 60s. (Gives time to warn/threaten people.)
  • -setnow Effects an immediate nick collision for that nick.
  • -halt Kills a pending 60s nick collision set with -set above.

• forbid (nick) Forbids anyone from using this nick. (For eg, it's a good idea to forbid people using the nick 'id' as users often type /msg id (mypassword) by accident. Worse when it's an oper id'ing to Operserv. Dont want someone collecting wayward passwords.) unforbid undoes this.

• noexpire (nick) Nicks normally expire after 8 weeks (modifyable server config). Operator, administrator and preferred user's nicks should be set noexpire. Use clearnoexp to unset this.

-- KenChase - 16 Oct 2004