Server Commands/ACCOUNT
| Line 1: | Line 1: | ||
| - | '''Command Token:''' AC | + | {| class="wikitable" width="25%" style="font-size: 85%; text-align: left;" |
| - | + | |- | |
| + | | '''Command Token:''' AC | ||
| + | |} | ||
<pre>ACCOUNT <numeric> <flag> <args></pre> | <pre>ACCOUNT <numeric> <flag> <args></pre> | ||
Revision as of 09:34, 4 October 2008
| Command Token: AC |
ACCOUNT <numeric> <flag> <args>
Examples:
1* Az AC ABAAC R Rubin 1037526164 -- New (standard) 2* Az AC ABAAC R Rubin -- New but No timestamp 3* Az AC AB A .15.1835576208 1037526164 -- LOC authorised 4* Az AC AB D .15.1835576208 1037526164 -- LOC denied 5* Az AC ABAAC U -- Unregister 6* Az AC ABAAC M Rewbin -- Rename
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.
