![]() ![]() What are my options?ĮDIT: Been messing around all night with tests/readings.ĬloudMounter or ExpanDrive might be my solution to access my whole google drive. but it MUST be "for my eyes only" and it must still sync with apps and services that are on my other devices and pull files from my google drive. edu Unlimited Google Drive and about 800GBs of Photos/Videos. TL DR: I want to SYNC about 250GBs of data with my. Is there a way to hide the data from them, including my google photos? If it's encryption that I need to do, will how I "encrypt" the data still allow the files to sync and autoupdate between my iMac and the cloud? Will the encrypted data still work with apps and services that pull files/data from my google drive to operate? Finally, should I also have a "backup" to this data? Or is the data on my iMac HD and in the Google cloud considered enough of a "backup"? edu but I am very very very not excited about how university admins can access all my data and I don't understand how to hide the data from the admins. I have an unlimited google drive (google photos reports X data out of 2PBs is used so I'm assuming I have 2 Petabytes) with my. ![]() I'm wondering if anyone can offer some advice. Please understand, that we have to finish the crypto core changes of version 0.8, before we can begin analyzing application-specific bugs.Hi DataHoarder Community, I've only been lurking for a few days and read several posts related to my needs but I can't figure out how to move forward with my needs. We have to test the combination of NetDrive/Cryptomator and ExpanDrive/Cryptomator respectively. We will have to identify the cause of these modifications. ![]() ![]() Regarding ExpanDrive: File modifications between write and read are severe problems and we're currently making authentication even stricter. We're currently working on making locking optional but I can not promise, that this will solve this issue. Your NetDrive errors may be related to this behaviour, we are aware of similar errors on SMB mounts. I don't know either of the two applications, so without testing this particular setup I can only guess: Cryptomator locks some files and not all file systems support locking. It allowed me to create the vault directly in the app, it did not throw delayed write errors, it did not throw device attached errors, but it did throw Cryptomator warnings about possibly malicious changes and any attempts to actually open the Cryptomator stored files failed in the Windows apps. I also went ahead and tried another product, ExpanDrive 5, for the Amazon Cloud Drive mapping and that also failed, though differently. I tried both with the same result (well, with local setting I got none of the delayed write failed but instead got more device attached to the system is not working). NetDrive2 has the option of mounting a cloud drive as "local" or "network".
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |