Search the Community

Showing results for tags 'chroot'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. Running Xiaomi R2D with ARM7L and uClibc. To make it work, I basically followed this tutorial on creating a chroot environment. I used Gentoo Stage 3 ARMv7a HardFP stage3-armv7a_hardfp-20160523.tar.bz2 and tried both btsync ARM 2.3.8 and btsync ARMHF 2.3.8. However, I still get this: root@XiaoQiang:/userdisk/data# chroot btsync-root /btsync/btsync Illegal instruction What I am doing wrong? Would appreciate any help I can get!
  2. Hi all, I just recently came across BTSync and plan on mass deployment. My main concern is that the "Select Folder" option in the WebUI (Linux) lists everything starting in '/'. Could you possibly have the WebUI chrooted to the "dir" location from the conf or introduce "chroot" as an available option? For example, user 'qwerty' would have something along the following set in the conf: "dir" : "/home/btsync/users/qwerty", "chroot" : "/home/btsync/users/qwerty", Then when user "qwerty" logs into the WebUI, and clicks "Add folder", their home/root path would be chrooted to the above value(s) and not '/' on the box. I'm sure others would like to see the same implemented in a multi-user environment. Detrimental common usage scenario: The average user will run the btsync daemon under the root account other than start it under a new/other system user. By doing so, the standard btsync user will be able to add otherwise sensitive file/folder locations to it's share via the WebUI - such as shadow hashes, plaintext database configuration files found on the server, etc. This poses a huge security risk for any shared environment as otherwise imposed system restrictions will be easily circumvented. I hope you take the chroot option into consideration