Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No support for ssh, sftp, scp or secure transports #441

Closed
desrod opened this issue Feb 23, 2023 · 2 comments
Closed

No support for ssh, sftp, scp or secure transports #441

desrod opened this issue Feb 23, 2023 · 2 comments
Labels
C-duplicate Category: This issue or pull request already exists

Comments

@desrod
Copy link

desrod commented Feb 23, 2023

Obviously a pretty big one, but why are SSH, SFTP, SCP not supported backends for rustic?

@aawsome
Copy link
Member

aawsome commented Feb 23, 2023

Thanks for opening this issue.

About SFTP: This is a duplicate of rustic-rs/rustic_core#11 (and SFTP actually is supported via rclone)

About SSH: This is no backend. rustic needs a storage backend where it can store and read files and list directories. SSH is a remote shell which of course can also be used as transport layer for a file transfer protocol, but then we are at SFTP.

About SCP: Here the functionality of listing directories is missing.

About secure transports in general: The REST backend supports accessing a REST server via https. Here are two use-cases:

  • run the REST server an a remote storage server and access it via --repository rest:https://<server>:port. There is also https://github.com/aawsome/rust-server.
  • run rclone serve restic which can expose the REST api to a remote client running rustic/restic. This use-case is especially interesting when using the --append-only option of rclone.

@aawsome aawsome added the C-duplicate Category: This issue or pull request already exists label Feb 23, 2023
@aawsome
Copy link
Member

aawsome commented Feb 26, 2023

IMO this boils down to SFTP support and therefore is a duplicate of rustic-rs/rustic_core#11.
I'm closing this issue - feel free to reopen if there is an aspect I didn't see!

@aawsome aawsome closed this as completed Feb 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-duplicate Category: This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants