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

Question: Moving files in gocryptfs #226

Closed
Suika opened this issue Apr 13, 2018 · 4 comments
Closed

Question: Moving files in gocryptfs #226

Suika opened this issue Apr 13, 2018 · 4 comments
Labels

Comments

@Suika
Copy link

Suika commented Apr 13, 2018

I have a question regarding a file move in gocryptfs.

Let's say I have a folder A that is reverse-mounted onto folder B.
The structure of A is /1/2/3/, and the folder 1 contains a file named test.txt.
Now I will copy the folder(contents) B somewhere else and mount it in forward mode onto folder C.

As the documentation states, the reverse mode uses deterministic encryption and per se will derive the IV from the encrypted path. Which to say will have the gocryptfs.diriv up to folder /1/2/3/.

And now the actual question. If I move the file test.txt in the C mount from the folder /1/ to /1/2/3/ will it use the diriv that the folder provides for the filename encryption like in reverse mode ?
And following from there, if I create the folder /1/2/3/4/ will it use the deterministic method or the standard urandom stuff for the diriv ?

Thanks in advance.

@rfjakob
Copy link
Owner

rfjakob commented Apr 14, 2018 via email

@Suika
Copy link
Author

Suika commented Apr 15, 2018

No, it will create a random one

Then the -aessiv option it is.

Thanks.

@rfjakob
Copy link
Owner

rfjakob commented Apr 16, 2018

This just switches the encryption mode from aes-gcm to aes-siv. It has no effect on diriv

@rfjakob
Copy link
Owner

rfjakob commented Apr 17, 2018

You may be interested in looking at #108 . If you also want that feature, please comment there!

@rfjakob rfjakob closed this as completed Apr 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants