• Content Count

  • Joined

  • Last visited

About glennpowers

  • Rank
    New User
  1. Problem: A small business business wants to share documents between employees. btSync Solution: “The IT person” installs btSync on a company computer system, creates a folder in it and gives the Full Access secret to employees and instructions for setting up btSync. Problem with btSync solution: an employee is fired. Chaos ensues as new secrets are generated, distributed, changes made to local btsync folders are lost, etc. Proposed Solution: Client software generates public/private key pair and sends the public key to a “client controller.” Client Controller responds with Full Access Secret(s) for client btSync DB(s), and Full Access Secret(s) for btSync Folders, encrypted with the client’s public key. Employees setup folder(s) and client software as operates the same as btSync currently does. Proposed Solution Implementation: “The IT person” installs “btSyncControl.” Employees install “btSyncControl” and send “Requests for Access” to “the IT person.” Using the Full Access Secret(s) for client btSync DB(s), the Client Controller(s) can monitor the status of individual folders. Before an employee is terminated, a Client Controller can send a “Wipe” instruction to that employee’s btSyncControl. Once the wipe is confirmed, the employee is informed of the news. An advantage of this solution is that Full Access Secrets can be securely be sent over insecure networks. Issues with proposed solution: Employees can copy files to non btSyncControl folders. They could do this with most solutions. Folder Full Access Keys will reside on employee machines. The keys could be changed with an extension to this protocol. Although, it is unlikely that “most” employees will attempt to extract the Full Access Key secrets before they are fired.
  2. Inspired by, I threw together a proof-of-concept using DokuWiki and btsync. Pages can be read in any text editor, use secret BBRS7WMRIUO4C4PUPN6KYRFUZHVHDRFVY Most editing of what little content is on the site was done in gedit on my notebook... cheers, glenn
  3. "BitTorrent will never work!" said countless people. Yes, what you are saying make sense. The thrust of your "Bottom Line" seems to be btsync should have a "hide incomplete nodes" option. Good suggestion. I'm not privy to the actual "current design and update logic." So, I really can't say. But, you raise some important points. Let me propose a use case: I share a "Summer Adventures 2012" folder with a few hundred photos. I send the r/o secret and a link to btsync download to a dozen friends. They install btsync and setup a r/o folder. Each looks through the folder and deletes some number of photos. Then, the deleted photos are fetched again. "add them to the .SyncIgnore" is not a viable option for most "average" users. IMHO, the users of r/o nodes should "fully control what happens in [their] r/o nodes." Even if that means they are divergent from r/w nodes. btsync should present some indication to the r/o users of how they are divergent and offer them options for convergence. r/w nodes should all eventually be consistent. If a btsync database file becomes corrupted on a r/o node, sync'ing should stop and users should be presented with a choice: sync folder to full copy OR (continue) stop sync'ing of folder OR delete folder from btsync (not filesystem). The btsync API should support "node status" and "folder status" messages. It should also accept the options suggested above for failure recovery and other divergence recovery options. And someone should write an SNMP interface to that.
  4. I just had the same problem. I'm running btsync v1.3.94 on Ubuntu 14.04 amd64 on two machines:. laptop connected to file server via ethernet, each connected to net via WiFi. They were syncing fine, then just stopped. I tried killling and restarted btsync on each. No connected devices shown. Rebooted both machines, sync web page worked fine on the file server, but showed no connected devices. sync web page on laptop did not show version or any Folders. Clicking "Preferences" did nothing. Killed/restarted btsync serval times, same result. Log file shows: [20140510 02:22:56.348] Loading config file version 1.3.94 [20140510 02:23:00.369] UPnP: Could not map UPnP Port on this pass, retrying. I noticed a btsync Folder was not mounted on my laptop. Mounted drive. Restarted btsync, worked. Drive was mounted when problem started, so that may be another problem. This is not good.