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
What happened:
We currently only support the proxying of http/https traffic.
What you expected to happen:
Having a way to proxy tcp data to enable having a memorable ssh endpoint for your tor hosted node for example.
Nice addition would be the possibility for us not to read traffic as it might be encrypted.
Say an ssh stream coming through wouldn't be something we can encrypt. For clearnet http/https this wouldn't be possible as far as this simple idea goes, but we might be able to look into this further.
Is this a BUG REPORT or FEATURE REQUEST?:
feature
What happened:
We currently only support the proxying of http/https traffic.
What you expected to happen:
Having a way to proxy tcp data to enable having a memorable ssh endpoint for your tor hosted node for example.
Nice addition would be the possibility for us not to read traffic as it might be encrypted.
Say an ssh stream coming through wouldn't be something we can encrypt. For clearnet http/https this wouldn't be possible as far as this simple idea goes, but we might be able to look into this further.
Copied over from: txtdirect/txtdirect#239
The text was updated successfully, but these errors were encountered: