-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add an command to execlude Ports #24
Labels
Comments
I think allowing ports makes more sense than excluding them |
I'm not sure if it makes any sense =\ Does anyone else need this feature? Please let us know (by reaction/emoji, for example). |
I think that both options are good, and can be used as mutually exclusive
option, but exclude has more sense at all.
Exclude let you exclude most common used ports, like 3128, 8080, 80, etc,
so your proxy will have less chances at basic port detection.
No one will test 65000 ports for every IP to check for proxy. Case of
backconnect doesn't even apply.
Include lets you... hum... filter by ports :D
~~ Self signed ~~
2017-10-04 17:25 GMT+02:00 Denis <notifications@github.com>:
… I'm not sure if makes any sense =\ Does anyone else need this feature? Let
us know (by reaction/emoji, for example).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHkwAsO1NI00nET_Hye0Vk7Vodu04MfYks5so6NWgaJpZM4KNsGc>
.
|
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Is it Possible to add an command to execlude specific ports? So it wouldn't grab Proxys with for example: Port 80, Port 8080?
The text was updated successfully, but these errors were encountered: