Replies: 2 comments
-
sorry, apparently I’ve already asked the first part 3 years ago and it was answered in issue #511 so please ignore the moving encrypted files between stores (so I use the same conf file or change the masterkey in the new store to match the one in the old one). the question re: the deterministic filenames remains however. and the other questions of course. unless I find out that those two were already asked (by me) and answered 🙈 |
Beta Was this translation helpful? Give feedback.
-
so #511 works just fine, tested it with a lot of files. so the moving "as is" question is done. I tried to create a conf file with the deterministic names on and changed the masterkey to the old working (diriv) conf one (which worked just fine) but the resulting conf file would not work on my old data at all. not displaying anything when mounted. you're all probably laughing now because it's obvious to everyone that this could never work but I tried anyway. does this mean, the only way to go from diriv to determ names is to actually decrypt and re-encrypt all data while moving it to a new store using a conf file with that flag on? it's about 2PB of data and I really, really want to get rid of dirivs. |
Beta Was this translation helpful? Give feedback.
-
since google wants to be massive ç"%R I'm moving my very large amount of data to another provider.
I figure server-side transfer is easier and faster and was wondering if I could just copy the encrypted data to the new provider if I set up gocryptfs there with the same password or what would be the way to getting around downloading/decrypting/encrypting/uploading?
also, can I create the new environment with the deterministic names setting enabled and still just server-side copy the files while dropping the dirivs and it'll work? probably not, already sound stupid. if not, is the only way to get rid of the diriv files the downloading/decrypting/encrypting/uploading way to a encryption created with that setting on?
I've been using gocryptfs for 6 years now and it's always performed and worked fine. and easily enough, for someone like me.
but, still, here's another question I couldnt really find a proper answer to or better yet, a comparison. I was looking into using rclone crypt. almost only for the simple reason it will let me mount the cloud folder on e.g. my shield and other linuxy devices. I cant do this with gocryptfs, right? assuming no, the only difference between those two methods would be, that with rclone (crypt) the shield would do the mounting and reading and decrypting and such and in the gocryptfs case, my computer's OS would do all that and then hand it over to the shield or plex or whatever?
one more: cryfs' incremental synchronization, isnt that a good thing and would speed up uploads/syncs? wouldnt everyone want to have that or aint it a big deal in reality? trying to find out if I understood this correctly....
Beta Was this translation helpful? Give feedback.
All reactions