You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Thu, 31 Dec 2020 at 9:11 am Matti Paksula ***@***.***> wrote:
$ chisel server --reverse -v
2020/12/31 00:08:04 server: Reverse tunnelling enabled
2020/12/31 00:08:04 server: Fingerprint 1mS6n2APlkBh30oiqG1yb79RHzQezhGQqj3ogVTrauI=
2020/12/31 00:08:04 server: Listening on http://0.0.0.0:8080
2020/12/31 00:08:20 server: session#1: Handshaking...
2020/12/31 00:08:20 server: session#1: Verifying configuration
2020/12/31 00:08:20 server: session#1: tun: Created
2020/12/31 00:08:20 server: session#1: tun: SSH connected
2020/12/31 00:08:20 server: session#1: tun: proxy#R:1080=>socks: Listening
2020/12/31 00:08:20 server: session#1: tun: Bound proxies
^-- would be nice to know the client address
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#233>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE2X46PYIIRM446ZFBIFEDSXOQSZANCNFSM4VOYQDCQ>
.
@jpillora
Hi,
Can we also add in debug logs some simple detection for probing (if somebody wants to get in for example)? Using -v I see requests to chisel when reverse proxy mode is enabled.
^-- would be nice to know the client address
The text was updated successfully, but these errors were encountered: