JennyElv

Members
  • Content Count

    5
  • Joined

  • Last visited

About JennyElv

  • Rank
    New User
  1. Is it possible that files in that folder are open in an other application? I had similar issues while I tried to sync a "working folder" of an application - it simply did not complete. After closing the application it magically continued and completed the sync process. I currently suspect that BTsync cannot access open files ...
  2. Maybe I found the problem: On my machine having all the files, there was an application running which had open some files in the to be synced folder ... After closing this application, all files could suddently be synced. So it seems that open files can block btsync to continue/work as expected!?
  3. Having the same problem here. Version 1.0.134, both on Windows 7 64bit. Folder to sync ~ 750MB, 2500Files. When I add the folder to BTSync on the second machine - it almost immediately starts creating all folders and fetches a bunch of files (~30 MB) ... and then it completly stops.
  4. Hi, I tried to run BTSync on my older IcyBox 4220. When trying to start the arm version of BTSync I only get this message: root@icybox:/tmp# ./btsync Illegal instruction The CPU in the 4220 is a FA526 arm processor ... is this procesor too old? Or am I doing something wrong? thanks for any hint. JE
  5. I think that is not completely true - as especially with application like BTSync there is an addition issue to consider: Usually, once my machine got hijacked, a attacker would need to copy all my important data - which requires him to locate the data and a lot of time till everything is copied over the line. In addition - as this usually takes a longer time - there is a good chance to get identified, interrupted, etc. ... With tools like BTSync this is different: A attacker only needs to steal the .sync folder, which usually is small and can be copied quickly to any location in the world ... then the attacker only needs to sit back and watch my important files being delivered to his machine more or less automatically. This happens after he already left my compromised machine ... there is also a good chance that "I" not at all realize that a new machine is syncing with my files ... So I think the .sync folder is some sort of security hole - which should be protected by additional (optional) encryption/passphrase, expiring keys, ...