Feature: Client-Only Transparent Proxy #239
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
obilodeau
approved these changes
Jul 21, 2020
|
I don't see what change fixes #203. |
https://github.com/GoSecure/pyrdp/pull/239/files#diff-1b1cfb078e7a51aa889289ef74c8c7f0R273 |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for client-only transparent proxying (See
docs/transparent-proxy.mdfor firewall setup) For scenarios where a subnet is to be spoofed (via ARP, for instance) but connections to the target server should be direct.Caveats: It will fail noisily (impossible to connect) if the target servers have NLA enabled. Nothing we can do about this.
Also this includes some bug fixes:
--payloadwithout having a player running.Missing: