[DOCS-1511] Backup - Public key for SCP restores Created: 13/May/13 Updated: 14/Jun/13 Resolved: 14/Jun/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Steve Briskin (Inactive) | Assignee: | Allison Reinheimer Moore |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: | |
| Days since reply: | 10 years, 35 weeks, 5 days ago |
| Description |
|
A customer can restore a backup using SCP, where we will SCP the snapshot to them. Rather than providing login credentials, they can add our public key to trusted hosts. Provide information on how to do this (key information, and how to add it to trusted hosts). And a recommendation to remove it after the restore for security reasons. Key: On *nix and macosx, should be added to user's ~/.ssh/authorized_keys file. Maybe provide a screenshot of what it should look like. Cailin will add abridged instructions on the UI. Please keep her in the loop. |
| Comments |
| Comment by auto [ 14/Jun/13 ] | |
|
Author: {u'username': u'schmalliso', u'name': u'schmalliso', u'email': u'allison.moore@10gen.com'}Message: | |
| Comment by Allison Reinheimer Moore [ 05/Jun/13 ] | |
|
All good, I probably should've realized since I documented the "Backup and Restore Public Key" option in the Settings documentation. I've updated the instructions and it's back in code review: http://codereview.10gen.com/10848028/ | |
| Comment by Cailin Nelson [ 04/Jun/13 ] | |
|
Okay, here's how it works now... The big change is that there is no longer any such thing as "the public key". We're now generating a public key (and a private) key on a per user basis. Before a user can initiate a restore via SCP they need to go to Settings and choose "Backup and Restore Public Key". Then they type in a password (used to encrypt the key) and we generate a public/private key pair. We store the private key (encrypted) and display the public key to them. They need to take the displayed public key and add it to the .ssh/authorized_keys file on appropriate server on their end. (I.e. the server to which they want us to copy the restore files). Very sorry about forgetting about this change, which was part of the June 3rd release. | |
| Comment by Cailin Nelson [ 19/May/13 ] | |
|
We've had to change the key. The key is now
Attaching screenshot of the abridged documentation that occurs in the app. |