mtucker

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by mtucker

  1. Your suggestion would be sending unencrypted files through the sync process rather than the entirety of the encrypted volume. Should sync become compromised in some way, the attacker would be getting the unencrypted data that you worked to protect with TrueCrypt..

    So, if worried about the tunnel being compromised then file-based encryption rather than volume based would definitely be the way to go.

  2. I'm also tinkering with syncing a TrueCrypt volume across several machines. This is yielding some headaches, as once a change is made, btsync looks like it has to transfer the entire volume. I guess this is because the checksum of the encrypted volume has changed, and any sliding window-based checksumming would also think that each and every block has changed?

    If I remember correctly the TrueCrypt volume is an encrypted virtual disk that mounts to a folder or drive letter. If this is the case you would probably want to aim BTSync at the mount point rather than the virtual disk file.

  3. The company I work for has 32 satellite locations and no real servers anywhere but HQ. We recently shipped out a set of identical computers, one to each location, so I snuck a 1TB drive into all of them to store "local" copies of large installers like Office. Just after they shipped I happened to run across BTSync, so I took remote control of the computers at satellite locations and used BTSync as a service to keep my satellite install shares synchronized with our main install share here at the HQ.

    Finished the first "test" system on Friday, added a second system today and it's pulling data from both "original" locations as it should, even with the satellites setup in read only.

  4. I saw this mentioned briefly in step 6 but I completely overlooked it so I figured I would go into details based on information I found the hard way.

    BTSync stores all configuration files under:

    NT5 (Windows XP/Server 2003/Server 2003r2): "%USERPROFILE%\Application Data\BitTorrent Sync"

    NT6 (Windows Vista/7/8/Server 2008/Server 2008r2/Server 2012): "%USERPROFILE%\AppData\Roaming\BitTorrent Sync"

    This means all BTSync settings are user-specific. By default the installation method mentioned here runs the service using the LocalSystem account. Because there is no way to log in to LocalSystem it is impossible to configure BTSync under the LocalSystem account. To get the service to work properly you must log in with a named account, configure the application, then set the service to log in using that named account.

    For example, if you are using a computer on a domain:

    01) Create an account on the domain controller for the BTSync service

    02) Log into the computer you will be running the service on using the BTSync account

    03) Install BTSync and setup your shares

    04) Exit BTSync, install the service as detailed in the first post and verify it can be started

    05) Open Services.msc, stop the BTSync service and open the BTSync service properties

    06) Click the Log On tab

    07) Select the "This account:" bullet

    08) Enter the fully qualified user name

    09) Enter the password for this account

    10) Save changes and start the service with the new settings

    Tested this Friday night, works like magic.