David F GliddenandClaude
389febb161
- 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>
SSH Configuration
⚠️ Security Notice
Never commit private keys to git! This directory contains only:
- Example SSH config (sanitized)
- Public keys (safe to share)
- Setup scripts
Setting up SSH on a new machine
- Generate new SSH keys (if needed):
# GitHub
ssh-keygen -t ed25519 -C "your_email@example.com" -f ~/.ssh/github
# General purpose
ssh-keygen -t ed25519 -C "your_email@example.com" -f ~/.ssh/id_ed25519
- Restore SSH config:
cp ~/dotfiles/ssh/config.example ~/.ssh/config
# Edit ~/.ssh/config to add your actual hostnames, users, and key paths
- Set correct permissions:
chmod 700 ~/.ssh
chmod 600 ~/.ssh/config
chmod 600 ~/.ssh/*_key
chmod 644 ~/.ssh/*.pub
- Restore existing keys (if you have encrypted backups):
# Decrypt backup
gpg -d ~/dotfiles/backups/ssh_[timestamp].tar.gz.gpg | tar -xzf -
SSH Config Best Practices
- Use SSH key agent:
ssh-add -K ~/.ssh/your_key - Use different keys for different services
- Enable 2FA where possible
- Regularly rotate keys
Backup Strategy
Run the backup script to create encrypted backups:
~/dotfiles/backup-scripts/backup-sensitive.sh