chiark / gitweb /
resolver: Actually set port in resulting ca's
authorIan Jackson <ijackson@chiark.greenend.org.uk>
Thu, 23 Oct 2014 22:49:17 +0000 (23:49 +0100)
committerIan Jackson <ijackson@chiark.greenend.org.uk>
Thu, 23 Oct 2014 23:16:27 +0000 (00:16 +0100)
commitf3d19c02998616d3677eff83bff97fd0d91ddbff
treeef1e4deddd9ebb1532e54541bc835e151f8afdcc
parentbfc34affaf5e80fe6a85bbcc4c302005154b4531
resolver: Actually set port in resulting ca's

This got broken in 2093fb5c `comm etc.: Provide comm_addr_equal'.

We mistakenly removed the code that copied the port from q, along with
the code that copied the adns answer from ra.  (The sockaddr that
comes back from adns obviously doesn't have a port number in it.)

As a result all actual DNS resolutions would result in an unuseable
sockaddr with port==0.

Signed-off-by: Ian Jackson <ijackson@chiark.greenend.org.uk>
resolver.c