Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of this change?
I hope this doesn't fly in the face of best practice. I have some platforms for which I do not allow password authentication at all. Only keys. I'd like to be able to store the key in the config (or environment variable) with the rest of the parameters rather than carrying it around in an external file to deploy along with the rclone config.
So i'd allow for a config parameter to store the actual key rather than only read a file system file. This would also enable tools that abstract the filesystem from the app running rclone to work correctly here (RCX for android for example).
command:
--sftp-key-pem (actual key)
config:
key_pem = (actual key)
I was thinking since the config file doesn't allow multi-line that I would force a sane delimiter (\r\n and \n).
Thoughts?
Was the change discussed in an issue or in the forum before?
no. It was a simple change so figured i'd just do a PR for review.
https://forum.rclone.org/t/add-ssh-key-to-config-file-rather-than-filesystem-pointer/16404
Checklist