LinkSharing
on the linked table is set to Yes
There isn't direct way to share encrypted files using just WebDAV.
Indirectly you could theoretically set up one way backup from WebDav to e.g. S3 using S3Drive, and then share from S3. Not ideal, but perhaps it might make sense to have additional backup of your data anyway.LinkSharing
on the linked table is set to Yes
There isn't direct way to share encrypted files using just WebDAV.
Indirectly you could theoretically set up one way backup from WebDav to e.g. S3 using S3Drive, and then share from S3. Not ideal, but perhaps it might make sense to have additional backup of your data anyway. rclone
on the back-end and/or we allow users to host it themselves (for privacy reasons) and connect from S3Drive, as an alternative to native browser support. (edited)rclone
on the back-end and/or we allow users to host it themselves (for privacy reasons) and connect from S3Drive, as an alternative to native browser support. (edited)V2 cipher
to keep compatibility with Rclone.
We plan to merge it to Rclone mainlaine, but didn't have time to finalize work: https://github.com/rclone/rclone/issues/7192rclone config file
location.~/.config/rclone/rclone.conf
which is exactly the location where Rclone would place its config had it be running from host natively.filename_encoding = base64
as default is set to base32
.
Other ones we set explicitly, but they're actually matching defaults:
https://rclone.org/crypt/#crypt-directory-name-encryption
https://rclone.org/crypt/#crypt-filename-encryption