mount
we're Rclone wrapper with some convenience features.
You can achieve pretty much the same using CLI.
There are some minor differences, but these are related to e.g. crypt support of V2 cipher: https://github.com/rclone/rclone/issues/7192 (which isn't yet part of Rclone).
We may need to do some tweaks in the future to deliver certain features: https://s3drive.canny.io/feature-requests/p/file-offloading-cloud-nas-tiered-storage.exe
that's not signed using some specific certificate which we're not eligible for just yet: https://github.com/Azure/trusted-signing-action/issues/72#issuecomment-2790298284
As long as you you got S3Drive .exe
from our official release page: https://github.com/s3drive/windows-app/releases/tag/1.12.6 you should be fine.
We have also release through Microsoft Store: https://apps.microsoft.com/detail/9nx2dn9q37ns?hl=en-GB&gl=CZ if you don't want to install .exe, however current version is 1,5 months old and there were plenty improvements since then.
In a few days we will pass Microsoft certification and latest 1.12.6 shall be present on Microsoft Store as well.
This year hopefully we will be able to signed cryptographically our .exe
releases on Windows, we do that already on other platforms Android, iOS, macOS and partially on Linux. (edited).exe
that's not signed using some specific certificate which we're not eligible for just yet: https://github.com/Azure/trusted-signing-action/issues/72#issuecomment-2790298284
As long as you you got S3Drive .exe
from our official release page: https://github.com/s3drive/windows-app/releases/tag/1.12.6 you should be fine.
We have also release through Microsoft Store: https://apps.microsoft.com/detail/9nx2dn9q37ns?hl=en-GB&gl=CZ if you don't want to install .exe, however current version is 1,5 months old and there were plenty improvements since then.
In a few days we will pass Microsoft certification and latest 1.12.6 shall be present on Microsoft Store as well.
This year hopefully we will be able to signed cryptographically our .exe
releases on Windows, we do that already on other platforms Android, iOS, macOS and partially on Linux. (edited)[1.11.0] - 2024-12-23
release, and it should work on Windows and Linux (not all releases work exactly the same though). On macOS it requires some special treatment which we didn't have chance to apply.
We'll try to get back to these over the next few weeks and perhaps we can get this to work.rclone cleanup
yourself (applies probably for desktop only, as setup on mobile is cumbersome), as S3Drive uses rclone.conf
, so you can refer to same remote names./etc/apt/sources.list
) e.g. from some Medium article without doing due diligence.
There are other way to secure your credentials (e.g. Rclone password), but that's not yet integrated into S3Drive: https://s3drive.canny.io/feature-requests/p/rclone-encrypted-config (Some users reported that they managed to use Rclone encrypted config, but it "blocks" S3Drive when app starts and expects password to be provided in console [Stdin])
crypt
improvements: https://github.com/rclone/rclone/issues/7192 and even tough we're not experts we understand some bits.
Unofficial Proton wrapper is more of a concern, mostly because it doesn't utilize any document API from Proton, it doesn't have sufficient amount of development and maintenance. Additionally, we're not exactly sure what's Proton's stance regarding this wrapper and Rclone and its future.
Despite these challenges, it's gaining popularity and there are more and more users using it.
I am somewhat convinced that it's gonna stay with us, even without Proton support, but if Proton decides they don't like it, it will be an arms race which won't benefit anyone.
crypt
improvements: https://github.com/rclone/rclone/issues/7192 and even tough we're not experts we understand some bits.
Unofficial Proton wrapper is more of a concern, mostly because it doesn't utilize any document API from Proton, it doesn't have sufficient amount of development and maintenance. Additionally, we're not exactly sure what's Proton's stance regarding this wrapper and Rclone and its future.
Despite these challenges, it's gaining popularity and there are more and more users using it.
I am somewhat convinced that it's gonna stay with us, even without Proton support, but if Proton decides they don't like it, it will be an arms race which won't benefit anyone.
rclone cleanup
yourself (applies probably for desktop only, as setup on mobile is cumbersome), as S3Drive uses rclone.conf
, so you can refer to same remote names. crypt
and use that key to encrypt/decrypt UI updates on both ends.
Added feature item: https://s3drive.canny.io/feature-requests/p/security-improvement-encrypt-ui-updates-for-rclone-crypt-back-ends (edited)--config
flag, e.g. rclone cleanup --config=/path/to/rclone.conf
or if you've copied Rclone config to default location you wouldn't need to use a flag at all.
https://forum.rclone.org/t/rclone-config-create-with-json-from-previous-config/46897/2?u=tomekitshared
Then each user could have their own folder/prefix encrypted using key that only they know. https://s3drive.canny.io/feature-requests/p/rclone-configuration-support-encrypted-vaults
Using some S3 providers, e.g Backblaze, you can restrict API key by path: https://www.backblaze.com/apidocs/b2-create-key
shared
folder and their own JoshEncrypted
by generating 2 separate API keys.
Even if you generated a single API key without any limit prefix
, then your users (nor you) can't decrypt encrypted contents of other users, since that data is encrypted.
However with that setup some privacy is leaked, as you (and other users) could look up into encrypted structure of other users and have understanding of file size, folder hierarchy and last update date.
In the future we'll support encrypted vaults: https://s3drive.canny.io/feature-requests/p/rclone-configuration-support-encrypted-vaults meaning that you'll be able to combine different locations/folders/prefixes using different encryption strategies.
UPDATE:
We could certainly think of adding some webhooks or status.json
file, but first we would need to understand the use case and see if there isn't any feature that may solve your use case, that we plan on building anyway. (edited)$ rclone about Koofr:
Total: 10 GiB
Used: 519 MiB
Free: 9.493 GiB