Explore use of passwords, player keys, roles, and command verification

[oubiwann]

Notes:

• Creation process:
  • User connects via SSL Telnet
  • User enters the registration shell and selects the create option
  • User provides email and new password
  • User is sent an email with a verification code
  • User confirms verification code in SSL Telnet session
  • Secret player key is displayed to user and they are instructed to save it
• Re-generate process:
  • User connects via SSL Telnet
  • User enters the registration shell and selects the regen option
  • User provides email and new password
  • User is sent an email with a verification code
  • User confirms verification code in SSL Telnet session
  • Secret player key is displayed to user and they are instructed to save it
• Logging in:
  • User provides password used when registering
  • User may optionally provide player key when connecting to a game with a particular player, but they may only do so if connected to the server via SSL Telnet
  • If Telnet was used instead, switching to shells with elevated permissions will not be possible
• Shells with elevated permissions:
  • If player key was not provided when connecting to game:
    • admin aliases to admin shell will not work
    • player will have to explicitly switch to the admin subshell, providing the player key when doing so
  • If a player key was provided:
    • admin aliases to admin shell will work
    • optionally, a player may explicitly switch to the admin subshell without having to provide the player key
• Verification:
  • All commands passed in elevated modes will be verified using the player key
  • The user will submit a command
  • The user's session will be examined for the player key and the command will be signed
  • The command will be sent to the command processor with the user's name
  • The command processor will perform a lookup of the player key and the granted roles for the given user name
  • The command processor will sign the passed command with the key found when looking up the user
  • The command processor will compare the signature it generated and the signature passed by the user and proceed only if they match
• Should only be transmitted over an encrypted connection