![]() Known hosts - Secret - QR code - WebUI - Con fig file. ![]() Once you've got your profile(s) set, you can control which one(s) btsync loads with the /etc/default/btsync config file.Device name - Updates - Notifications - Limits - Relay server - LAN - DHT - SyncArchive. This client is running on my remote server, so I enable LAN encryption and the relay server, and disable LAN searching.I disable the built-in web UI, because no.I disable upnp and set a specific listening port so I can easily control access with my firewall ( ufw).!/usr/lib/btsync/btsync-daemon -config // // in this profile, btsync will run as my user ID // DAEMON_UID=gemma // Here's what I did on my Ubuntu 13.04 server: We don't set things up manually in Ubuntu, son! Per usual, setting up the Windows and Android clients is a fairly brainless process setting up a Linux client is a little more exciting. I just replaced my KeePass triggers, my cron job and my Android rsync with one tool, without handing any of my data to a third party. It'll automatically keep 30 days worth of version history. Once the tracker matches up some peers, it's done it never sees the synced data, encrypted or otherwise, because the peers talk to each other directly.Īs a bonus, the btsync client does local backups by default. There are millions of hashed keys hanging out on the trackers right now, looking for matching peers, completely secure. The hashes can't be forged (at least until somebody breaks SHA-2), and the original keys are needed for decryption. If you're outside a LAN, you can enable MAGICAL THINGS: btsync can send a one-way hash (SHA-2) of your key up to a BitTorrent tracker, and match up peers by matching up hashes. Just btsync peers and a shared key, no external servers necessary. ![]() If you're running behind a LAN, that's all you need. ![]() The actual content transmission is just like regular BitTorrent, except with 256-bit AES encryption (based, again, on the folder key). Any other btsync peer (computer running the syncing client) with the key can sync from the folder, and no peer without the key can even see it. The key uniquely identifies your sync folder. You hand it a folder to sync, it hands you a 21-character key (password). Long story slightly less long, I've been mixing KeePass database triggers with a remote cron job and an Android port of rsync for a couple years. I also disable password authentication over SSH, so the native KeePass syncing capability is out-which isn't that big of a deal, because it doesn't work in the Android port anyway. I could run something like SparkleShare, but that seems like overkill for one lousy file. I don't want to rely on free cloud storage providers, so I substitute various incarnations of personal servers, and I sacrifice the nifty auto-syncing clients. Syncing the database to all said devices, on the other hand, has always been a minor headache. I like that it's free, that it runs on all my devices and that it integrates with any password-protected application (not just my browser). I've been using KeePass for password management for roughly five years, ish.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |