-
Notifications
You must be signed in to change notification settings - Fork 8
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
Issue with processing http://127.1 URL #1
Comments
Hi there, here all the information. If you need something more let me know! OS version
go version
go env
Http Server Code
Curl outputs
Server debug output
|
@padovah4ck thanks. i believe that's all i need. at first glance, everything seems pretty normal. i'll take a close look later today. |
I did some digging around in the For example, when running on Kali, the same setup as you, I am able to reproduce the issue. In this scenario, Go uses the If we take MacOS as another example, Go has a special case, where it forces a All that being said, the behavior you're seeing does not have any security implications. It's fails before We'll have a discussion if it makes sense to introduce a default configuration which would force the same DNS behavor on all OSs. Given the developer comments in the Until then, I'll leave the issue open. |
Thanks @v1ktor0t that's crystal clear! I didn't mean to address a security concern with this :)
Now all works as "expected" and go uses native resolver :) Thanks again. |
A Tweeter user mentioned that, when running the CTF challenge locally, requests such as:
return the following error message:
It looks like the URL
http://127.1
was interpreted as a hostname instead of an IP address and Go tried to resolve it.To easily debug the issue, it would be helpful to have:
EnableDebugLogging(true)
to the configAdditionally, does this behavor happen with a payload like
http://127.0.0.1
or any other variant of the loopback IP is used, or is it justhttp://127.1
causing it?The text was updated successfully, but these errors were encountered: