ortreum
-
Posts
3 -
Joined
-
Last visited
Posts posted by ortreum
-
-
Hello,
is it really necessary to have a static port number? If not please change it to a random one like in utorrent. This should make it harder to be blocked by local firewalls (ie. chinese GFW). As a little extra this port can change every x minutes and switch between udp and tcp. or misuse common ports like 21, 25, 80, ...
I am using torrent sync to backing up domains from a linux server. The program has a --dump-sample-config parameter. But it would be extremly nice to convert these binary config data that only can be changed via the web ui to a text like for reusing it on other maschines.
btsync --dump-current-configand you have all keys and directorys and all the other preferences in a nice clean config.conf
Michael
-
Maybe there's a simple solution. First the port should be able to change randomly on each start or the program tells the other nodes what the next port will be. Misuse ordinary ports 21, 22, 25, 80, 443 and protocols tcp, udp. There are ways ... and they should be implemented as automatically running features.
To update the software every new version can get an unique key for downloading the program via the torrent network. So it only needs one person in da hood who already has it and all the chinese guys can get it.
Be more creative
Relay-Network For Obfuscation
in Feature Requests
Posted
Hello,
let's say every node has a relay feature by default (some low amount of upload capacity). Assuming 90% are switching it off. Then there should be still serveral thousand nodes out there to forward data (without opening the data blocks) in an acceptable speed. So if there is no direct way between the private nodes to sync each other it might be done via some relay nodes. This can make the whole thing more robust against blocking and censoring mechanisms.
Michael