iswrong

Members
  • Posts

    164
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by iswrong

  1. Sorry, I should've been more specific, I meant Linux. Checking who signed the app bundle in OS X indeed works great: % codesign --display -vv BitTorrent\ Sync.app[...]Authority=Developer ID Application: BitTorrent, IncAuthority=Developer ID Certification AuthorityAuthority=Apple Root CA[...](Just running the app only gives the guarantee that someone signed with a keypair created with *any* Apple developer account. )
  2. Thanks! Would it be possible to provide checksums, or even better: sign the downloads, in the future?
  3. I wrote this down in a little more detail here: http://danieldk.eu/Posts/2015-10-18-erp.html
  4. Just leave the folders that you don't want to sync disconnected on #3. If you don't want them to be visible at all and use the Pro version (which propagates added folders to all machines added to an identity), create a separate identity.
  5. A read-only share cannot propagate changes to folders on other machines. It does not mean that the files in that folder cannot be overwritten. In other words, if the desktop uses a read-only key and the phone a read-write key, changes on the phone are synced to the desktop. Changes on the desktop are not synced to the phone (since the desktop only has read-only access to the folder).
  6. A 'standard folder' in 2.2 is a '1.4 folder'. The 2.0-style folders are called 'advanced folder' in 2.2 and require the Pro version to create. So, schematically: 2.2: 1.4 folder -> Standard folder 2.x folder -> Advanced folder
  7. Last time I tried this, it only syncs files that are currently in that folder, but not new files. Has this changed?
  8. I am kind of messy and let OS X's Spotlight do most of the work of locating files. In general, this works better for me, because it is often more obvious what content you are looking for than which categorization you gave to it at the time. I make broad directory-based categorizations for documents and more fine-grained directory structures for photos, since they tend to be harder to search. I have a desktop machine with a disk that is large enough to store all of my BTSync folders and use Arq to make encrypted off-site backups. On my laptop I use partial sync to save space. I also have two always on low-power BTSync peers with plenty of storage, but didn't have time yet to set up off-site backups on these yet (which would reduce the amount stuff needed on the aforementioned desktop).
  9. I know that it's the first 33 characters (!) (not bits, the keys are log2(32) * 32 = 160 bits). Yes, but you always know it, since current versions of BTSync list it (Preferences for the relevant share -> View keys, and it's there). No need to count the 33 characters anymore or using 'head -c' or whatever . (Of course, only when you use a 'D' or 'E' key.) If you do this programmatically, of course, then just taking the first base32-encoded characters of the read-only key is the most sensible approach (but ensure that you created a 'D' key, or you are just distributing the read-only key.)
  10. That shouldn't work. If you have an encrypted read-only node, the read-only key is longer. From the spec: Note that there is one exception: an encrypted-read-only secret is nearly twice as long (65 symbols), its body consisting of 2 keys - Data access key and Data encryption / decryption key, each of 20 bytes Base32 encoded value. http://sync-help.bittorrent.com/customer/portal/articles/1628254-key-structure-and-flow Such a key is only generated when the read-write key starts with a 'D', which is what this topic is about. When you do what you suggest, you just get a share with no peers (because the keys don't match up). --- So, the procedure is, create an 'A' key (read-write) and re-add it, changing the initial 'A' with an 'D'. Or using a command such as the one that I posted to generate a 'D' key directly. After that, the interface will show the correct (double-length) read-only key and even the encrypted read-only key. (I thing you looked at an existing share which already had the encrypted read-only secrets, and copied/trimmed the read-only key from there. Try it with a new share which has an 'A' key.)
  11. Note: it seems to me that this approach weakens the key, since you are you are squeezing a certain range non-uniformly into another space. Just use Base32 . dd if=/dev/urandom bs=20 count=1 | /usr/bin/python -c "import sys;import base64; sys.stdout.write(base64.b32encode(sys.stdin.read()))" | sed 's/^/D/'There is probably a Perl module as well .
  12. No, you don't need Pro. The free version creates 1.4-style folders, and works exactly as 1.4 since 2.2 (except that you can be invited to new-style folders). The Pro version gives you access to some extra features, such as 2.0-style shares (where you can modify permissions in hindsight, etc.) and selective sync.
  13. But Bittorrent Sync 2.2 can now be purchased as a perpetual license. So, you give money once, and get all the nice 2.0 features (selective sync, automatic sync of folders on all devices, the new folder permission system, etc.).
  14. Pre-2.0 and 2.0 folders work quite differently: Pre-2.0 does not have the concept of an identity. If you create a folder, it gets a read-write key. A read-only key can be derived from this key. You can then add either the RW or the RO key to a peer and it will start syncing. But you can see each peer as independent - there is no identity tying peers. In 2.0 you create an identity, which is basically a digital certificate. When you link a new device, that device gets the same certificate as the original device. The permissions for a particular folder is associated with the identity. E.g. if you create a new folder with an identity, your identity has read-write permissions for that folder. If I share a folder with you read-only and you accept it, your identity has read-only access to that folder (across all devices with that identity). This means that all devices using a particular identity will have the same permissions for a particular folder. If you want to create a folder which is read-write on one machine and read-only on another machine, they currently need to have different identities. In principle, you could make as many certificates as you want (e.g. one per device), however, this comes with some disadvantages: since you license an identity, you would need a license for each identity where you want Pro features. BTSync 2.2 changed some things: if you are not a Pro user, you cannot create 2.0 type folders anymore (only < 2.0), though a Pro user can share a 2.0 folder with you. Moreover, without Pro, shares don't propagate among peers (adding it to one peer won't automatically add it to other peers with the same identity). In your situation, I think there are two possibilities: - Use the same identity on the three Macs, but a different identity on the server. Then share folders read-only with the server from the macs or vice versa. I think this would imply that you need two Pro licenses (since both identities need to be able to share a 2.0-style folder). - Use pre-2.0 folders, since this would allow you to create read-write and read-only keys for each folder.
  15. For me the FAQ that you linked says: Q: I’m a current Pro customer and I use Sync for personal use. I noticed that “Priority Support” is no longer offered for personal/individual licenses. Do I still get support? A: Only customers who have a Pro subscription license will receive Priority Support. The fragment that you quote isn't even there?
  16. Only when you explicitly change your license to a perpetual license. When you think of it, it makes sense: support staff costs money, and it is hard to give priority support for a one-time ~40 dollar fee, given the salary level of tech employees . So if you need priority support as opposed to normal support, the yearly fee is quite a bargain.
  17. //!/usr/lib/btsync/btsync-daemon --config{ "storage_path" : "/iomega/btsync-aux/daniel", "display_new_version": false, "disk_low_priority" : true, "lan_encrypt_data" : true, "rate_limit_local_peers" : false, "folder_rescan_interval" : 600, "folder_defaults.delete_to_trash" : true, "folder_defaults.use_lan_broadcast" : true, "folder_defaults.use_relay" : true, "folder_defaults.use_tracker" : true, "sync_trash_ttl" : 365, "folder_defaults.known_hosts" : "", "use_upnp" : false, "webui" : { "directory_root" : "/iomega/btsync/daniel", "listen" : "0.0.0.0:8888", "force_https" : true, "ssl_certificate" : "/home/daniel/.sync/daniel.crt", "ssl_private_key" : "/home/daniel/.sync/daniel.key" }}While at it, my systemd unit file (/etc/systemd/system/btsync@.service) [Unit]Description=BitTorrent Sync for %i[Service]Type=simpleUser=%iExecStart=/opt/btsync/btsync --nodaemon --config /home/%i/.sync/sync.confWorkingDirectory=/home/%iRestart=always[Install]WantedBy=multi-user.targetAs you can see from this setup, the configuration is expected in a user's home directory under .sync/sync.conf . This allows a per-user BTSync setup. Also, if the daemon fails for some reason (in the past it crashed every once in a while), it is automatically restarted. I can restart the instance of user 'daniel' with: sudo systemctl restart btsync@daniel.serviceThe service for this particular user can be started at every boot using: sudo systemctl enable btsync@daniel.service(The nice thing about this setup is that multiple persons can have a BTSync instance on one server, but everything is automatically started and monitored using systemd.)
  18. It seems that some configuration file keys have changed, e.g.: folder_defaults.use_dht Run btsync directly to see the errors. Simply removing that configuration key worked for me. Since the PPA seems to be abandoned indeed, maybe I should post my nice systemd multi-user BTSync configuration .
  19. I think one of the important questions is: can I (as a Pro user) share an advanced folder with someone who does not have a Pro license? I didn't have time yet to try this . To answer my own question: Source: http://help.getsync.com/customer/en/portal/articles/2112392-folders Nice!
  20. Although I was not a vocal opponent against the 2.0 licensing (I purchased a Pro subscription a couple of months ago), I would like to thank you for listening to your users and adding more options! The perpetual license fits my personal use better, so I switched to that and the procedure was flawless. I think the license changes make it easier to promote BTSync among friends and colleagues. Thanks again!
  21. You can just associate the new machine to your identity (following the initial steps) and it will be Pro automatically. See: http://help.getsync.com/customer/portal/articles/1901247-sync-private-identity-linking-my-devices?b_id=3895
  22. Are you using exactly the same directories for OSes? Which filesystem?
  23. I don't want to distract from your original question, since I cannot help with your original question, but unfortunately that does not say (too) much, it's only an upper bound. For example, memory mapped files are counted towards resident memory, although they don't actually use that memory (the operating system loads pages into memory as needed). So to conclude whether btsync is actually a memory hog, you have to look at the resident set and subtract memory used by shared libraries and any mmapped files (see the pmap command on Linux).
  24. Memory hog? Each instance on my Pi generally takes ~40-60MB memory (tens of gigabytes in shares). My Pi has 1GB memory*. $ free -m total used free shared buffers cachedMem: 927 909 18 46 149 622-/+ buffers/cache: 137 789Swap: 99 0 99In other words, there is ~789MB free memory (after subtracting OS buffers/caches). * I assume that the amount of memory being used is correlated to the number of files, so there may be more degenerate cases.
  25. I guess this depends on your NAS, but on our Pi we run a couple of BTSync instances with different identities (of different persons).