-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
Pivoting/Tunnelling #28
Comments
Great idea, I am working on designing the protocol and the architecture. |
1. Add port forwarding methods #28 2. Detecting Public IP address 3. Refine web UI
Released in v1.4.3. |
|
1. Add port forwarding methods #28 2. Detecting Public IP address 3. Refine web UI
1. Add port forwarding methods #28 2. Detecting Public IP address 3. Refine web UI
1. Add port forwarding methods #28 2. Detecting Public IP address 3. Refine web UI
Can you please provide an example also for push, dynamic and internet modes? TLS client -> TLS server -> Platypus There is no need in upgrading the session, and creating a tunnel is not possible. TLS client -> TLS server -> Platypus -> Tunnel [Create|Delete] [Pull|Push|Dynamic|Internet] [Src Host] [Src Port] [Dst Host] [Dst Port] [TLS|NOT ENCRYPTED] [TCP|UDP] If you can explain how the upgrade and tunnel commands work I can give a more accurate idea and point you to a correct suggestion(: |
It would be nice to be able to use compromised targets as proxies to allow pivoting into a target's network. This feature would greatly improve the utility of the tool and enable it to be used as a flexible and powerful C2 framework for pentesting engagements.
The text was updated successfully, but these errors were encountered: