"Move Dropbox locationDropbox will stop syncing in November"
Je to spôsobné tým, že Dropbox prestáva podporovať “nezvyčajné” súborové systémy. Jediným podporovaným súborovým systémom v Linuxe bude ext4. Stane sa tak od 7.novembra tohto roku. Niektorí užívatelia hlásia chybu pri zašifrovanom ext4. Pôvodne k tomuto žiadne oficiálne stanovisko neexistovalo. V podstate ešte stále nie. Je dostupná iba konverzácia s podporou, kde sa jasne hovorí, že šifrovanie (LUKS/ecryptfs) nebude podporované. Objavilo sa aj údajné riešenie ako prevádzkovať Dropbox na zašifrovanom ext4.
Hi everyone, on Nov. 7, 2018, we’re ending support for Dropbox syncing to drives with certain uncommon file systems. The supported file systems are NTFS for Windows, HFS+ or APFS for Mac, and Ext4 for Linux. We’ve updated our desktop requirements accordingly here. A supported file system is required as Dropbox relies on extended attributes (X-attrs) to identify files in the Dropbox folder and keep them in sync. We will keep supporting only the most common file systems that support X-attrs, so we can ensure stability and a consistent experience. If you received a notification, but are running one of the supported file systems, it's possible that you may have recently had a computer linked that was running an unsupported file system but have been since upgraded, or that computer is no longer being used. Hope this helps to clarify matters!
Všetky požiadavky na používanie Dropbox.
X-attrs alebo Extended file attributes sú rozširujúce vlastnosti súborového systému, ktoré umožňujú súborom pridávať špecifické metadáta neslúžiace samotnému súborovému systému. Podpora X-attrs linuxovými súborovými systémami: ext2, ext3, ext4, JFS, Squashfs, Yaffs2, ReiserFS, Reiser4, XFS, Btrfs, OrangeFS, Lustre, OCFS2 1.6 a F2FS.
Jedným z možných vysvetlení, prečo skutočne došlo k tomuto kroku je, že Dropbox ako šifrovací kľúč ku prihlasovacím údajom používa f_fsid z funkcie statvfs(). Na ext4 je je vždy vrátená tá istá hodnota. Na iných súborových systémoch sa táto hodnota môže meniť. Takže Dropbox získa iný kľúč, vďaka čomu synchronizácia zlyháva pretože nemá prístup ku prihlasovacím údajom.
I don't believe xattrs are the problem. The Dropbox client uses an unrelated feature – the f_fsid field in statvfs() – as an encryption key for your account credentials (hostkeys). On ext4 this fsid is static, but on XFS it is dynamic (based on the major:minor device number, which can change if you e.g. swap SATA ports). If the fsid or the inode number changes, the key won't fit, so the client discards all configuration and tells you to re-link the account. This isn't used for anything else besides encrypting hostkeys and so could be easily replaced with only the inode number, or an xattr, or libsecret, or python-keyring, or even /etc/machine-id. Found this out the hard way several months ago, after moving $HOME to another disk (yes, including xattrs – I double-checked those) and having the client mysteriously unlink from the account. After some tracing and searching, found one of those "dropbox hostkey forensic tool" GitHub repos which revealed how everything works. Wrote my own tool, which decrypted the config using the old key and reencrypted with the new one – and it magically relinked. Later on, I mentioned this on the Dropbox forums where another user was having the same problem (client mysteriously unlinking after reboot). They verified it and contacted Dropbox support; support told them "we don't support XFS"; and uh, two months later this thread happened. Sorry about that? edit Aug16: talk about possible solutions
Jay, this is really problematic. You cite lack of xattrs as a reason, but that's simply not correct, i.e. XFS has supported xattrs for decades. I've been a primary XFS developer since 2001, and I've worked on ext4 since around 2007 as well. I can't imagine any reason why ext4 would be a requirement over any other posix-compliant filesystem that supports xattrs. If your team has any technical questions, please reach out to me, I'd be happy to assist. Thanks, -Eric
I can verify. According to support, the dropbox devs have confirmed that LUKS/ecryptfs will not be supported, even if ext4 is the host. (Zdroj obrázku)
In my case, I keep an encrypted home directory on ext4 file system, on Ubuntu 16.04, ext4 file system. And I was notified on end of sync support on November, 07. Does that mean I should sacrifice security and place Dropbox on insecure file system instead, to make your client happy?
Are you aware of, encryption is nearly mandatory for any company in Europe? If you loos one device with an unencrypted disc/SSD containing customer data, you have to inform every single customer about that! If I understood correct, you prevent ext4 users from encryption. Good luck with that decision!
Guess what... Dropbox downloaded daemon on Linux Mint and it refuses move dropbox folder to an NTFS drive (as always did) because only EXT4 is supported on LInux. Happens that drive must be NTFS because it is shared with Windows!!! I am paying my valued money to Dropbox to get things running smoothly. How NTFS is not supported on LInux? What the *#*& of a service is this??? I have payed another 1 year service in June and I want my money back.
Slashdot refers to this thread here. It's kind of strange why Dropbox officially didn't respond in any social media, since the background for the decision (Xattr support) isn't valid - there were mention of many widely used Linux flesystems that do support Xattrs. So, why Linux users are supposed to start using unencrypted ext4 only ? It would be nice to see the official company response to the mentioned multitude of users'comments.
Is anyone using hardware disk encryption and seeing the dead-in-November issue? My Lenovo laptop currently has password protection on the hard drives through the BIOS and disk controller, but the file system I'm using is XFS, not EXT4 so I can't answer this question yet. This might provide a path for European users to continue to use Dropbox and stay within the four corners of GDPR regulations -- Dropbox sees the bare ext4 (or NTFS, &c) filesystems, yet if the laptop grows legs your data would still be safe from ne'er-do-wells, thus satisfying the GDPR regulations.