Server Commands/ACCOUNT
m |
|||
| Line 12: | Line 12: | ||
ACCOUNT is intended to be issued by service bots on the network. Login-on-connect systems based on IAuth cause the server to introduce the client as logged in, just as during net junctions. | ACCOUNT is intended to be issued by service bots on the network. Login-on-connect systems based on IAuth cause the server to introduce the client as logged in, just as during net junctions. | ||
| + | |||
| + | |||
[[Server Commands|(Return to Main listing of Server Commands)]] | [[Server Commands|(Return to Main listing of Server Commands)]] | ||
Revision as of 19:26, 12 September 2008
Command Token: AC
<prefix> AC <target> <flag> <account> [<timestamp>] For LOC: <prefix> AC <target> <flag> .<fd>.<cookie> <username> :<passphrase>
The ACCOUNT command implements a login system for ircd-darenet. When received by the user's server, the user--specified by <target>, the user's numeric nick--is considered logged in to the <account>. The optional <timestamp> parameter specifies a timestamp that can be used to determine which version of the user's account the user is logged in to; this can be used by service bots as a way of distinguishing hacked accounts from legitimate user logins after a password change--which would raise the timestamp.
The account is only used by ircd-darenet for pre-logging in users while they're connecting, for umode +R and cmodes +R/M, host hiding and for application of channel bans and silence masks. ircd-darenet also propagates the account name (and timestamp, if set) when re-introducing users during net junctions, so that service bots can see that the user is logged in and set their appropriate internal state. ircd-darenet does not otherwise use account information or timestamps.
ACCOUNT is intended to be issued by service bots on the network. Login-on-connect systems based on IAuth cause the server to introduce the client as logged in, just as during net junctions.
