sergey@bt

Employees
  • Posts

    86
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by sergey@bt

  1. Unfortunately re-adding folder will not help here. It should be fixed when all clients are updated to 1.0.130. We are planning to enable auto-update in a day or two.

    If you need it sooner, you may try the following workaround (but please test it locally first):

    1. Install 1.0.116 (1.0.130 will not allow such trick), preferably on Mac or Linux - since initially your issue was caused by bug in Windows version.

    2. Sync it with your folder with full access secret

    3. Shutdown Sync and disconnect computer from network

    4. Set time to 2015

    5. Run Sync and remove selected files, make sure Sync sees that files are removed (files counter in UI)

    6. Shutdown Sync and return time back

    7. Connect network and start Sync again

  2. There are 3 points of contact with BitTorrent infrastructure: tracker, relay, check for update service (listed above HTTP request). If you don't use any of it - we will not get any information about you.

    As for brute force - a lot of things in cryptography is based on a fact that there is no other way to decrypt data besides brute force attack (e.g. you can not recover private key from public). We believe 160 bit random secret is strong enough here.

  3. BTSync uses FSEvents API to get file notifications on OSX. Additionally BTSync does rescan of the shared folder once in 10 minutes. So if it you see file updates only in 10-15 minutes, it means file notifications do not work for you. Can you please try the following:

    1. Make sure fseventsd process is running (this is a system process responsible for file system logging)

    2. Try to add any other folder (e.g. ~/btsync) and check if it works. We saw few cases when fseventsd stopped to send events for particular folders.

    3. Try to reboot your Mac.

  4. You need to make sure btsync is able to communicate with Internet using UDP, not just your Linux VPS where you run VPN. You may try to analyze network traffic to port 3000 (which is our tracker port). btsync on your Windows machine should send and receive UDP packets to/from this port.

    BTW how do you route your Internet traffic through VPS? Do you run NAT or proxy on VPS? btsync does not support proxy.

  5. As a first step can you please check if BTSync is able to send and receive UDP packets via your VPN channel? If you have any shared folder, BTSync should send UDP packets to tracker and it should be able to receive reply. If you enable debug log, it should be visible there. Also you can just monitor BTSync port with some network analyzer (Wireshark for Windows).

  6. Did you put btsync executable into shared folder? Please move it out.

    By default on Linux btsync creates .sync folder with metadata in the same folder where executable is located. If you put .sync folder into btsync shared folder, it may create infinite loop.