| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
add backup encryption and interactive restic init - Plain `skm backup` now warns loudly that the bundle contains unencrypted private keys - `skm backup --encrypt` produces a .tar.gz.enc via openssl AES-256-CBC (same envelope as `skm export --encrypt`); `--password-file` for scripted use - `skm restore` auto-detects the .enc suffix and decrypts before extracting; matching `--password-file` - `skm backup --restic --init` replaces the manual password-file + config setup with an interactive flow that prompts for the repository URL (with examples for local, S3, R2, SFTP, B2) and password, then runs `restic init` and only writes restic.json on success - Missing restic config / password now surfaces a hint pointing at --init instead of fatal-ing - RequireInitializedResticRepo skips local-FS checks for scheme- prefixed repo URLs (s3:, sftp:, b2:, etc.), since restic will surface backend errors at invocation time Closes the "Backups have a security hole" item in PLAN.md. | 3 个月前 |