btron

New Members
  • Content Count

    4
  • Joined

  • Last visited

About btron

  • Rank
    New User
  1. works great - for my Android-Phone. but, any glue to get a read/write-sync for my... ...iPhone?
  2. going to getsync.com instead using getsyncapp.com is the solution. * getsync.com uses a valid https-certificate, thank you!
  3. tried to download the "brandnew" 2.2.1-qnap-package https://download-cdn.getsyncapp.com/2.2.1/QNAP/BitTorrentSync_2.2.1_arm-x19.qpkg => wrong server certificate [firefox] => did you're server got hacked??? "wget" shows:the same: wget https://download-cdn.getsyncapp.com/2.2.1/QNAP/BitTorrentSync_2.2.1_arm-x19.qpkg <https://download-cdn.getsyncapp.com/2.2.1/QNAP/BitTorrentSync_2.2.1_arm-x19.qpkg --2015-10-12 00:22:40-- https://download-cdn.getsyncapp.com/2.2.1/QNAP/BitTorrentSync_2.2.1_arm-x19.qpkg Resolving download-cdn.getsyncapp.com... 54.230.46.168 Connecting to download-cdn.getsyncapp.com|54.230.46.168|:443... connected. ERROR: cannot verify download-cdn.getsyncapp.com's certificate, issued by â/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2â: Self-signed certificate encountered. ERROR: no certificate subject alternative name matches requested host name âdownload-cdn.getsyncapp.comâ. To connect to download-cdn.getsyncapp.com insecurely, use `--no-check-certificate'. ...loading the current "stable"-file works fine: wget -O btsync.tar http://download.getsyncapp.com/endpoint/btsync/os/linux-arm/track/stable --2015-10-12 00:24:24-- http://download.getsyncapp.com/endpoint/btsync/os/linux-arm/track/stable Resolving download.getsyncapp.com... 67.215.238.66 Connecting to download.getsyncapp.com|67.215.238.66|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 4784187 (4.6M) [application/octet-stream] Saving to: âbtsync.tarâ btsync.tar 100%[=====================================================>] 4.56M 1.37MB/s in 3.3s 2015-10-12 00:24:28 (1.37 MB/s) - âbtsync.tarâ saved [4784187/4784187]
  4. thanks for the info, hoping for the release-software!!! ...same issues here. Verified with Linux/Ubuntu 14.04 and Linux/QNAP, too. I think, this is broken by design since filenames and paths do not have an encoding; the OS only deals with sequence of bytes. Individual applications may choose to interpret them as being encoded in some way... it's not allowed, for my opinion, to assume, filenames could/should/etc be in "UTF-8"-encoding. The only not allowed-byte-Value in Filenames is NUL, isn't it? --- Impossible to use btsync for any data until this is fixed.