Live data from Hacker News

My one-liner Linux Dropbox client

lpan.io

41–50 of 165 posts

Re: My one-liner Linux Dropbox client

#41
post #13

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4. What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

Ext4 does support encryption. [0] https://lwn.net/Articles/639427/

Re: My one-liner Linux Dropbox client

#42
post #28
post #24

Since it is being used with systemd a systemd path unit could be used to monitor the file system removing the need to use entr.

Thanks, didn't know systemd can do that [0]! I must grudgingly admit that it seems to be quite useful, though I still don't like having a single app doing all that stuff. But that's off topic... :) [0] https://blog.andrewkeech.com/posts/170809_path.html

Both path units and entr use the inotify kernel API on Linux. If your needs get more complex, there are python, perl, etc, APIs for the inotify libraries.

Also, if you have an older linux distro that predates inotify(), there's similar functionality within auditd that will log changes to a file with a tag of your choosing, then you can tail the file.

Re: My one-liner Linux Dropbox client

#45

Earlier quoted context omitted.

Could be problematic if the image is huge.

You could use something like gocryptfs that encrypts at the file level

Cryptomator is another cross-platform alternative for file-level encryption: https://cryptomator.org

Also includes first-class support for cloud syncing apps.

Re: My one-liner Linux Dropbox client

#46

Dropbox is a no no for one simple reason - there is no end to end encryption. Unless I don't know something? I wouldn't want a disgruntled employee to fiddle with my files.

After e2e encryption, my second largest feature request is a .dropboxignore file

I don't understand why they don't have it even after all these years.

Re: My one-liner Linux Dropbox client

#47
post #13

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4. What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

Doesn’t work on ZFS either. I dropped Dropbox because of this.

Re: My one-liner Linux Dropbox client

#48

Earlier quoted context omitted.

Is there any Dropbox-like service that lets you control your own private keys, without resorting to the ugliness of uploading an encrypted image to Dropbox?

I think syncthing wins here. Not at rest, mind, but since you control the endpoints that should be okay.

Even though it's proprietary, Resilio Sync does encrypted peer to peer sync, plus it allow encryption-only nodes. These contribute bandwidth, but cannot decrypt the data.

Re: My one-liner Linux Dropbox client

#49
post #47
post #13

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4. What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

Doesn’t work on ZFS either. I dropped Dropbox because of this.

Why would an application like this care what file system it’s running on?

Re: My one-liner Linux Dropbox client

#50
post #13

> Recently, the proprietary Dropbox Linux client dropped support for all Linux file systems except unencrypted ext4. What the heck. Anyone has more information about that? Any announcement? And why would it fail to work on an encrypted (LUKS?) ext4 FS when encryption seemed to me to sit below the filesystem (since AFAIK ext4 doesn't support encryption itself)?

It's FUD. ext4 with LUKS, which is what pretty much everyone is using on a desktop, is still working and the client supported.

No, it's not FUD. encrypted ext4 is encfs and ecryptfs, not xy on LUKs, and yes, they did drop support.
Post reply on HN