Allow --resolve <host:*:address> #1264
Comments
Couldn't this be a security issue? I.e. downgrading a
This seems impossible now. |
Well all existing and future security issues regarding --resolve should
be noted in the --resolve paragraph there on the man page.
|
Which is why it says it is a sort of alternative. The other main reason is that the internal DNS cache already uses host name + port number in the lookup so doing it independent of port number needs more work. I'm not against the idea, I just think it is a fairly niche use case so I will probably not work on this myself. I don't think it has a security impact, as it only changes what IP to use for a given name + port provided in the URL. That can already be changed by changing |
The option |
Thank you, this idea is now mentioned in the TODO document! |
I am currently trying to get libcurl working with c-ares, and I am interested in implementing this feature to get localhost urls working @bagder Pre-filled DNS entries should work with c-ares, right? |
Disregard that, I just read the source code and this looks a bit… more interesting than expected. I guess, I will have to look into #1386 or something |
Man page has
Real /etc/hosts doesn't require a separate entry for each port number!
I.e., 65536 entries if one wants to cover all 65536 ports!
So please allow e.g.,
--resolve <host:*:address>
if one wants to coverall ports.
And
--resolve <hostA:*:address1> --resolve <hostA:4444:address2> ...
to allow making all ports go to address1 except certain ones to address2...
If
<host:*:address>
is ugly, then perhaps use<host::address>
or<host:address>
or all three.The text was updated successfully, but these errors were encountered: