Files
dotfiles/backups/ssh/RESTORE_INSTRUCTIONS.md
David F GliddenandClaude 389febb161 🚀 Complete machine migration setup with encrypted backups
- Added comprehensive configuration files for seamless migration
- SSH, GPG, Karabiner, iTerm2, Neofetch, SwiftBar configs
- Pass license management system with templates and documentation
- Enhanced shell functions with MAS updates and moon phase tracking
- Comprehensive encrypted backup system (GPG AES256)
- Included encrypted backups of all sensitive data
- BBEdit as default editor with proper configuration
- Fixed shell compatibility issues
- Merged existing .zsh configs with improvements

Security:
- All sensitive data is GPG encrypted (.gpg files)
- Private keys excluded from version control
- Only configs and encrypted backups are tracked

Following prime directive: durable, thoughtful solutions

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>
2025-07-28 23:10:36 +02:00

47 lines
1.0 KiB
Markdown

# SSH Keys Restore Instructions
## Decrypting and Restoring SSH Keys
To restore from backup: `ssh_keys_20250727_132554.tar.gz.gpg`
### Step 1: Decrypt the backup
```bash
gpg --decrypt ssh_keys_20250727_132554.tar.gz.gpg > ssh_keys_20250727_132554.tar.gz
```
### Step 2: Extract the archive
```bash
tar -xzf ssh_keys_20250727_132554.tar.gz -C ~/
```
### Step 3: Set correct permissions
```bash
chmod 700 ~/.ssh
chmod 600 ~/.ssh/config
chmod 600 ~/.ssh/*_key ~/.ssh/id_*
chmod 644 ~/.ssh/*.pub
```
### Step 4: Add keys to SSH agent (if needed)
```bash
ssh-add ~/.ssh/your_key_name
```
## Security Notes
- Keep this encrypted backup in a secure location
- The backup contains your private keys - treat it as highly sensitive
- Consider storing a copy in a different location (cloud storage, external drive)
- Test the restore process periodically
## Backup Contents
This backup includes:
- SSH configuration file
- Private keys found in ~/.ssh/
- Corresponding public keys
- Proper directory structure
Created: Sun Jul 27 13:26:00 CEST 2025
System: 15.5