(I don’t use google drive for myself, maybe some other user might say more about this) Browsing around the forum shows that people already using Cryptomator in combination with Google Drive File Stream and seems to work. To answer a): Browsing around the internet reveals that the main point would be that with Google Team Drives you’re forced to use Google Drive File Stream. In contrast to that approach Cryptomator tries to be as system agnostic as possible and therefore uses either common interfaces (like WebDAV) or relies on third party programs (for Windows it’s Dokan) resulting in a maybe slower, but also more general and also protocol save approach (not using any windows specialities and so on).
#Cryptomator vs boxcryptor driver#
So, in addition to this question, would Cryptomator be suitable for a) Google Team Drives and b) for business use?Īt first, i only know little about BoxCryptor.Īs far as i know BoxCryptor installs its own windows driver yielding a deep windows integration. However, this is massively disruptive for our business - and we are looking for something better. Thanks to Cryptomator, only you have the key to your data in. These keys can be stolen, copied, or misused. Most cloud providers encrypt data only during transmission or they keep the keys for decryption for themselves. It allows you to protect your cloud data by yourself and independently. We keep providing debug logs, and they keep providing experimental versions of the software which work for a time. Cryptomator is a simple tool for digital self-defense. Other software might not be impacted by these quirks as much because Boxcryptor has to work with Google Drive File Stream in a more “low-level” way than most other software. Sometimes Google Drive File Stream behaves different than any other “regular” filesystem and this can break things in Boxcryptor which are unexpected.
At the same time, Google is moving fast and that’s not always a good thing, especially because the virtual drive of Google Drive File Stream is not always following filesystem standards. This means we can only start adapting Boxcryptor to changes to Google Drive File Stream as soon as everybody else receives the new version. Unfortunately, Google releases updates to Google Drive File Stream in a rapid sequence and Google does not provide us with early access to new versions. So my question is, how is Cryptomator different in this respect? Boxcryptor have told us the following:
#Cryptomator vs boxcryptor update#
Every update causes problems (can’t save, open files etc.). We’ve been using Boxcryptor with Google Drive (OS: Windows 10) for several months, but it is clear that BC cannot handle Drive File Stream.
0 kommentar(er)
