Add --hostname on the client

[essoojay]

Hi,

thanks you for this, is it possible to add --hostname --header option and if --sni implementation is possible as well on the client?

thanks

[MarcelCoding]

Hi, it's really hard to understand what you are trying to say. Could You write one sentence about every option you would like to be implemented and how it should change the current behavior.

[essoojay]

Hi,

i lifted this from Chisel, here: https://github.com/jpillora/chisel

you may want to check it out further.

--proxy, An optional HTTP CONNECT or SOCKS5 proxy which will be
used to reach the chisel server. Authentication can be specified
inside the URL.
For example, http://admin:[email protected]:8081
        or: socks://admin:[email protected]:1080

--header, Set a custom header in the form "HeaderName: HeaderContent".
Can be used multiple times. (e.g --header "Foo: Bar" --header "Hello: World")

--hostname, Optionally set the 'Host' header (defaults to the host
found in the server url).

--sni, Override the ServerName when using TLS (defaults to the 
hostname).

i hope it clarifies a little more.

[MarcelCoding]

What is the advantage of zia compared to chisel?

[essoojay]

What is the advantage of zia compared to chisel?

Have not been able to test as i would, but its quite simple and hopefully faster than chisel

what am thinking is like:

obfuscation.

Am not good in all of this, but maybe you can understand it this way:

a typical simple chisel client string looks like (just as an example)

./chisel client -l 443 --auth xxx:xxx --hostname www.bing.com

where --hostname (www.bing.com) is never blocked on port 443

i hope that helps to understand it.

thanks

[MarcelCoding]

But what is chisel doing the command you described. Is it actually connecting to bing? You did not specify any other destination.

[essoojay]

oh, sorry about it, listening on server-ip 443

./chisel client -l xx.xx.xx.xx 443 --auth xxx:xxx --hostname www.bing.com

where xx.xx.xx.xx is server ip, port 443

[essoojay]

But what is chisel doing the command you described. Is it actually connecting to bing? You did not specify any other destination.

what am thinking is since you have mode with ws or tcp, if its possible to add to websocket header, something like --mode ws (Server: nginx bla bla Host: (cloudflare host or ip) or --mode tcp (tls sni: domain.com or hostname: domain.com

i hope you can have a look at this.

thanks