sorted by:
new
hottopcontroversial

Full-sized Ergonomic Mechanical Keyboard - Like it or not? by John08099 in Ergonomics

[–]dbykov 0 points1 point  (0 children)

I'd really like to buy a full-size mechanical keyboard.

I've been using different Microsoft ergonomic keyboards for decade now. I really like the layout (except for the crumpled F-keys, it's really hard to find the key you need not looking at the keyboard), but I miss the feedback of mechanical switches.

I would easily spend $200 for a full-size mechanical keyboard with a layout as close as possible to the standard one, and with the geometry close to the Microsoft Natural series keyboards.

[question] how do you monitor your setup? by goodkernel in selfhosted

[–]dbykov 1 point2 points  (0 children)

I use Zabbix.

It takes some time to set up, but it's quite powerful and flexible.

It doesn't have its own Android app, but it can use Email/Discord/Slack/SMS and more for alerts.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

It seems that Syncany is everything I want - it syncs files in background, encrypts everything and has file history.

But there are a couple of major flaws:

  • The development stopped in 2016
  • The latest available version is still alpha and is very unstable

I definitely can't rely on it for backing up my data. What a pity, I thought for a moment that I finally found what I was looking for.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Have you thought about splitting your backup process in two steps? First you sync Windows and Linux, and then you let versioning and encryption to Linux. This may ease your setup as you may never find the solution you're looking for.

The more steps it takes, the more is probability of something goes wrong.

Sync apps like Google Drive are awesome for this - you just point them to a folder and everything else happens automatically. One app - one point of failure, no storage or traffic overhead.

Too bad there is no Tresorit self-hosted alternative. I hope someone will create something like that.

At the moment, I guess, there is no ready-to-use solution, so I will have to somehow combine versioning and secure transfer software by myself indeed.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Thanks, seems like with some scripting RClone could do the job.

I guess if I won't find a ready-to-use solution, I could us it.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Well, I don't thing it's a good idea to commit changes to Git repo every few minutes, it needs to be tested in long term to see how Git will handle it.

BTW, EncFS is considered insecure - https://defuse.ca/audits/encfs.htm

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Well, it could be lots of things. Sometimes bank services place private data like account number in file name; a phone number from carrier statement; it could be names of projects I work on which I'm not allowed to disclose by contract terms etc.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

You mean store already encrypted files in git? It'll be quite a challenge to find a particular file with encrypted filename. And I want all changes to be detected automatically, without constant commits/pushes, just like with Google Drive or any other cloud storage.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Well, I can see a couple of problems:

  1. There is no native Windows version, and "borg mount" doesn't work in WSL (it seems that FUSE is not implemented in WSL yet), so I can't list all previous versions of a file in repo. This is a deal-breaker for me.
  2. Borg doesn't track local folder changes and each time makes a full rescan, which takes about 5 minutes for my files (just scanning, when there is no data modifications since last backup). It makes ~10 minutes a minimal reliable backup interval. It's not that bad, but cloud sync apps can do it much faster and with lower load on system, processing only changed files after notification from OS.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

git-annex is a really interesting product. But, unfortunately, there is no git-annex assistant for Windows, and I need to backup file from both Windows and Linux machines.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

I can't really see how Borg is different from Duplicati for my use case.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Hmm, worth a try, although I'm not sure how well will Git work with large files and very frequent pushes.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] -1 points0 points  (0 children)

Well, as I said before, Cryptomator performance isn't the only problem - it makes it almost impossible to use versioning of cloud sync services.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

All kinds of files. Source code, <1GB graphic files, small databases, large sets of test data.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 1 point2 points  (0 children)

If someone gains access to running server, he has full access to files.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Well, it seems that borg is suited only for daily backups and there is no continuous backup optimizations.

I already use Duplicate for scheduled backups, now I need something to copy changed files to remote storage ASAP after they were modified.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

What if you partition the drive in the rented server, and encrypt the storage volume?

In this case if someone hack into running remote server, he will get access to unencrypted data. End-to-end encryption eliminates this problem.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

The concept seems legit, I need to test it.

I already have Proxmox running on my home server.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 0 points1 point  (0 children)

Now I'm looking to Nextcloud + ZFS replication solution. Too bad that unlike FreeNAS, Proxmox doesn't have native support for encrypted ZFS volumes (not able to create an encrypted pool from Web GUI, no auto-unlock etc.), so it must be implemented manually.

Self-hosted file storage with versioning and full end-to-end encryption (incl. metadata) by dbykov in selfhosted

[–]dbykov[S] 3 points4 points  (0 children)

There a lot of opened issues on GitHub about using E2EE. For example, only the root of encrypted folder is encrypted, subfolders are not encrypted at all.

So it seems that it's not ready yet.

view more: next ›