peterd
-
Posts
4 -
Joined
-
Last visited
Posts posted by peterd
-
-
You are using the wrong quotes. Take a close look at them. Most of them are straight, those are the correct ones. Some are titled a bit, those are wrong. Did you use Word to edit your config?
Good catch! No, I did not use Word, but I did copy the syntax directly from the PDF. Unfortunately I did not notice the curly quotes in the original, and furthermore assumed that when I pasted it into the terminal that the double-quotes I was seeing were the right ones (they certainly looked right).
Fixing the quotes did the trick. Thanks everyone.
-
I dumped the sample configuration, and it says this:
// Advanced preferences can be added to config file.
// Info is available in BitTorrent Sync User Guide.
So I pulled the options from the guide, and attempted to add them to the config file (using the ppa from here).
I'm no JSON expert, but I fail to see where I'm going wrong:
{
"pid_file" : ".btsync.pid",
"storage_path" : ".btsync",
"listening_port" : 0,
"check_for_updates" : true,
"use_upnp" : true,
"download_limit" : 0,
"upload_limit" : 0,
“disk_low_priority” : true,
“lan_encrypt_data” : false,
“lan_use_tcp” : true,
“rate_limit_local_peers” : false,
"webui" :
{
"listen" : "127.0.0.1:9999"
}
}
When starting with those options I get the following error:
Error while parsing config file: Unexpected end of config file (are you missing '}') ?
If I delete the 4 "advanced" options, it works again. Are they supposed to go in their own section? If so, what does that look like?
TIA,
Peter
-
I like the software in concept, and am considering using it in an enterprise environment. I am wondering if it is possible to specify my own tracker.
TIA,
Peter
Possible to specify my own tracker?
in Sync General Discussion
Posted
That's unfortunate. I was evaluating bt-sync for an enterprise solution, but inability to specify my own tracker creates at least 2 security vulnerabilities off the top of my head. First, anyone with access to the tracker is going to see the "secret" hashes, which means they can attach a client and slurp my data. Second, anyone can attempt to mine the hive by creating random hashes trying to find a collision. Admittedly the second is a longshot, but attackers are creative and resourceful. Also, as the service becomes more popular it will both become a more attractive target and correspondingly the likelihood of collision with a random string becomes more likely.