diff options
author | Rich Felker <dalias@aerifal.cx> | 2020-05-18 21:17:34 -0400 |
---|---|---|
committer | Rich Felker <dalias@aerifal.cx> | 2020-05-18 21:30:33 -0400 |
commit | fd7ec068efd590c0393a612599a4fab9bb0a8633 (patch) | |
tree | f7e4b3bf7e023ddfe8e464b5a71e0cb858bf4beb /src/math/exp.c | |
parent | 593caa456309714402ca4cb77c3770f4c24da9da (diff) | |
download | musl-fd7ec068efd590c0393a612599a4fab9bb0a8633.tar.gz musl-fd7ec068efd590c0393a612599a4fab9bb0a8633.tar.bz2 musl-fd7ec068efd590c0393a612599a4fab9bb0a8633.tar.xz musl-fd7ec068efd590c0393a612599a4fab9bb0a8633.zip |
set AD bit in dns queries, suppress for internal use
the AD (authenticated data) bit in outgoing dns queries is defined by
rfc3655 to request that the nameserver report (via the same bit in the
response) whether the result is authenticated by DNSSEC. while all
results returned by a DNSSEC conforming nameserver will be either
authenticated or cryptographically proven to lack DNSSEC protection,
for some applications it's necessary to be able to distinguish these
two cases. in particular, conforming and compatible handling of DANE
(TLSA) records requires enforcing them only in signed zones.
when the AD bit was first defined for queries, there were reports of
compatibility problems with broken firewalls and nameservers dropping
queries with it set. these problems are probably a thing of the past,
and broken nameservers are already unsupported. however, since there
is no use in the AD bit with the netdb.h interfaces, explicitly clear
it in the queries they make. this ensures that, even with broken
setups, the standard functions will work, and at most the res_*
functions break.
Diffstat (limited to 'src/math/exp.c')
0 files changed, 0 insertions, 0 deletions