Repository navigation
sshkeeper v0.7.4
sshkeeper v0.7.4 — repair already-synced cross-platform SSH keys
v0.7.4 completes the key-path migration for clients that had already joined a
sync space with v0.7.0/v0.7.1 before upgrading.
Fixed
- Retry unchanged remote keys when the local file is missing. A Windows
client that previously accepted a Linux profile but could not read its
/home/.../.ssh/...identity now re-applies the existing remote key even
when the key record itself has not changed since the previous sync. - Repair the profile in the same sync. The corresponding profile is
re-applied together with the key, soIdentityFileimmediately changes to
the receiving user's local Windows path. - Finish the shared-bundle migration. Once the key is readable locally,
the next synchronization replaces the legacy absolute key record with the
portable~/.ssh/...form.
Validation
There is now an end-to-end regression test for the exact upgrade state:
v0.7.1-style Windows database and sync state, Linux absolute IdentityFile,
missing local key file, followed by one v0.7.4 synchronization. The test
requires the key file to be restored and the profile path to be rewritten.