chisel
chisel copied to clipboard
Can chisel not use websocket or HTTP CONNECT?
I tried to capture the packet and confirmed that chisel uses websocket to transmit TCP traffic., like this:
If the firewall only allows HTTP traffic and websocket is not allowed, chisel will not work.
Can chisel only use HTTP?
I find a similar thing called Bidirectional-streams Over Synchronous HTTP (BOSH).
https://en.wikipedia.org/wiki/BOSH_(protocol)
yrjyrj123 how can I contact you ? Do you have Telegram ? WhatsApp , email ?.
I have Telegram. https://t.me/tomli123 😊
Any chance we can learn more about this feature request?
Chisel without websockets requires repeated requests. This is very slow and chisel was written to improve on a tool that did this (crowbar). It might be possible with http2, however i think chisel over plain http1 will never be supported.
On Fri, 18 Sep 2020 at 1:09 pm allfro [email protected] wrote:
Any chance we can learn more about this feature request?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jpillora/chisel/issues/131#issuecomment-694621943, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2X44UNUCHTQQ6R5CV4DTSGLFN5ANCNFSM4J62HBJQ .
That's too bad. I completely understand the performance impact http1 would introduce but it would definitely make chisel more of a tunnelling Swiss army knife if it had this as a transport option. A lot of orgs use web security proxies these days which still don't support WSS.
Chisel without websockets requires repeated requests. This is very slow and chisel was written to improve on a tool that did this (crowbar). It might be possible with http2, however i think chisel over plain http1 will never be supported. … On Fri, 18 Sep 2020 at 1:09 pm allfro @.***> wrote: Any chance we can learn more about this feature request? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#131 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE2X44UNUCHTQQ6R5CV4DTSGLFN5ANCNFSM4J62HBJQ .
it is using multiplexing on websocket or not ? also the fingerprint is only for authentication of connections or its also for encryption of data ?