mirror of
https://github.com/therealpaulgg/ssh-sync.git
synced 2026-04-26 16:05:51 +03:00
[GH-ISSUE #24] Use .ssh instead of .ssh-sync-data. Perhaps add a 'safe' mode #3
Labels
No labels
ai-generated
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ssh-sync#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @therealpaulgg on GitHub (Apr 26, 2023).
Original GitHub issue: https://github.com/therealpaulgg/ssh-sync/issues/24
Originally assigned to: @therealpaulgg on GitHub.
By 'safe' mode, if the user has keys currently in the directory, provide some kind of interface for the user to allow the user to prevent ssh-sync from overwriting keys.
This may apply to both 'upload' and 'download'
@therealpaulgg commented on GitHub (Mar 20, 2024):
We should review .ssh-sync-data and make sure that we aren't explicitly deleting files. It would be bad to overwrite files without the user knowing...
Perhaps prompt the user and let them know if a key will be overwritten and the contents are different from what is stored on remote?
Is the config ordered the same each time it is generated, or does the order vary?
Let's use sha256sum to compare current files to new ones & warn