MAXLOGINS in X

  1. History of MAXLOGINS
  2. New feature
  3. How do I use it?
  4. Someone else has authenticated as me!
  1. History of MAXLOGINS

    Several years ago, when X was upgraded and usernames were introduced as the method to login to X, there was a feature known as MAXLOGINS that allowed a user to choose the number of different nicknames that could log into his username at one time.

    This led to much abuse. Troublemakers were creating user accounts for their floodbots in order to flood channels set to +r (registered-users only). Furthermore, they used the Undernet host-hiding feature to hide their real IPs, making it very difficult for channel operators to keep the floodbots out.

    Unfortunately, this abuse led to the removal of the MAXLOGINS setting for normal users in December of 2002. Many legitimate users of this feature appealed to CService for its return, the most common reason being that, if a ghosted connection were logged into X, the ghost would have to timeout and disconnect before the user could login to X from his new connection. This often took several minutes.

  2. New feature

    To answer this problem, CService has recently introduced a feature that allows two nicknames to login to the same username at the same time. However, because this feature is only meant to combat the problem of having a ghost logged into X, it is not the same as the old MAXLOGINS feature. See below for more information.

  3. How do I use it?

    Unlike the old MAXLOGINS feature, with the new feature, both nicknames must be connected from the same IP address. This means that you cannot login once from home and once from a BNC, work, or school computer with a different IP. Also, if the original connection that was logged into X had identd enabled, the new connection's ident must match the old connection's ident.

    It is not necessary to submit any new command to X to enable this feature; just login to X normally. If you are already logged in from another nickname, and your IPs (and possibly ident, see above) match, you will receive a NOTICE from X on your old nickname similar to this:

    -X- jotun2!jotun@ip-5111.hostname.com has just authenticated as you (jotun). If this is not you, your account may have been compromised. If you wish to suspend all your access as a precautionary measure, type '/msg X@channels.undernet.org suspendme <password>' and contact a CService representative to resolve the problem. ** Note: You will NOT be able to use your account after you issue this command **

    You will receive the standard "AUTHENTICATION SUCCESSFUL" notice on your new nickname.

    If the IPs (or possibly the ident) did not match, you will receive an error on your new connection similar to this:

    -X- AUTHENTICATION FAILED as jotun. (Maximum concurrent logins exceeded).
  4. Someone else has authenticated as me!

    If you receive the notice above, but you did NOT login from a new nickname, it is possible that someone else is trying to abuse your account. Issue the command suggested by X:

    /msg x@channels.undernet.org SUSPENDME <password>

    This will suspend your username, meaning that no one (not even you) can use your account until it is unsuspended. You should be absolutely sure before submitting this command, as it requires the intervention of a Senior CService Administrator to unsuspend you. After submitting the command, join #usernames and ask for help.