Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add --hostname on the client #114

Open
essoojay opened this issue Dec 12, 2023 · 7 comments
Open

Add --hostname on the client #114

essoojay opened this issue Dec 12, 2023 · 7 comments

Comments

@essoojay
Copy link

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
Copy link
Owner

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
Copy link
Author

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:password@my-server.com:8081
        or: socks://admin:password@my-server.com: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
Copy link
Owner

What is the advantage of zia compared to chisel?

@essoojay
Copy link
Author

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
Copy link
Owner

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

@essoojay
Copy link
Author

essoojay commented Dec 13, 2023

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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants