fix incorrect transport name in obfs3_flashproxy, which was causing flashproxy registration to fail
fix chaining logic
- we actually want the second shim to listen on the callback port, not the first shim
- tor socks-connects directly to the first PT, it doesn't need a tcp-to-socks shim
Added a loading configuration file on the server side. The format is identical to the client configuration file except ClientTransportationPlugin is ServerTransportationPlugin