Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #6987

Closed
Open
Created Sep 27, 2012 by David Fifield@dcf

Rehearse email registration helper key compromise

What happens if the Gmail password or RSA private key in #6383 (closed) is compromised? We should simulate that situation, and document the steps needed to recover from it.

The steps to be taken probably include at least

  • Deactivate the Gmail account.
  • Create a new Gmail account (or use one already created in reserve) with a new password.
  • Set up a new application-specific IMAP password (see #6986 (closed)).
  • Install the application-specific password on the facilitator.
  • Generate a new RSA keypair and install on the facilitator.
  • Insert the new email address and RSA public key in the flashproxy-reg-email program.
  • Build new flashproxy-client packages with the new email address and public key.
  • Security announcement of new packages.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking