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

Request: Add project for comparison and benchmarking #7

Open
YipYup opened this issue May 3, 2018 · 7 comments
Open

Request: Add project for comparison and benchmarking #7

YipYup opened this issue May 3, 2018 · 7 comments

Comments

@YipYup
Copy link

YipYup commented May 3, 2018

Regarding: "If you spot an error or want to see a project added, please file a ticket!"

I'd like to request you compare performance with a locally mounted rclone crypt -- where the encrypted path is a local folder, and the decrypted path is also a different local folder.

https://rclone.org/crypt/

@rfjakob
Copy link
Owner

rfjakob commented May 15, 2018

Good idea, but I could not get it to work

[...]
Remote config
--------------------
[remote2]
type = crypt
remote = /tmp/remote2
filename_encryption = standard
directory_name_encryption = true
password = *** ENCRYPTED ***
password2 = *** ENCRYPTED ***
--------------------
y) Yes this is OK
e) Edit this remote
d) Delete this remote
y/e/d> y
[...]

Now mount:

./rclone mount remote2 /tmp/remote2.mnt

Write into mountpoint:

echo HELLO > remote2.mnt/foo47564

See what shows up in the encrypted dir:

cat ./rclone-v1.41-linux-amd64/remote2/foo47564 
HELLO

Uhm looks like did not manage to enable encryption?

@rfjakob
Copy link
Owner

rfjakob commented May 15, 2018

I did the tar extract test anyway: 57 seconds.

Looking at https://nuetzlich.net/gocryptfs/comparison/#performance , that's about 4 times slower than gocryptfs.

@YipYup
Copy link
Author

YipYup commented May 24, 2018

For rclone, you'd need to make two "remotes". The first would be the actual filesystem where you'd be storing the encrypted files. But you won't configure it as an encrypted store. Then the second rclone remote would be an encrypted remote that references your first remote, where you reference the first remote by its rclone entry name ie: encrypted:. The name is what is above in the brackets.

Hope that helps.

@fabiopesaju
Copy link

I would also like to see the rclone in the tests...

@bingoxo
Copy link

bingoxo commented Jan 12, 2021

any update on this ?

@rfjakob
Copy link
Owner

rfjakob commented Jan 12, 2021

Sorry but probably I will not do this myself. If somebody benchmarks and posts the numbers i can add them to the page, though.

@alexanderadam
Copy link

alexanderadam commented May 5, 2021

Sorry but probably I will not do this myself. If somebody benchmarks and posts the numbers i can add them to the page, though.

Just to clarify: the benchmark is relevant for the 'Performance check mark'?
I don't understand the check mark to be honest. 😉

Apart from that, RClone not only supports encryption with a lot providers but it also has an Android app (also on GitHub). Which might be especially relevant for people that were interested in issue 121.

Maybe at least the hint If you want to have easy access via your mobile device, use rclone or cryptomator or so would be useful.
Other solutions would otherwise require a shell and I cannot explain how to mount encrypted storage with a shell on their mobile devices for non-tech-savvy users. 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants