summaryrefslogtreecommitdiff
path: root/doc/libresolv.html
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2020-10-04 17:30:37 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2020-10-04 17:30:37 +0000
commit9ced0ee229c37f1090bf7a271722bd6c3963bb6c (patch)
tree92f80851d4a7fe5f5772fb7e1c5f1b8b96511fb5 /doc/libresolv.html
parente073208d761790b7986ced96515e284c1d8890c7 (diff)
downloads6-dns-9ced0ee229c37f1090bf7a271722bd6c3963bb6c.tar.xz
doc: fix URLs
Diffstat (limited to 'doc/libresolv.html')
-rw-r--r--doc/libresolv.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/libresolv.html b/doc/libresolv.html
index df24eee..ac5e027 100644
--- a/doc/libresolv.html
+++ b/doc/libresolv.html
@@ -34,7 +34,7 @@ Here are a few reasons why.
The same people who wrote BIND wrote libresolv. That is the amount of
trust you can place in libresolv. Ten years ago, the security status
of libresolv looked like
-<a href="http://cr.yp.to/djbdns/res-disaster.html">this</a>. I am not
+<a href="https://cr.yp.to/djbdns/res-disaster.html">this</a>. I am not
confident that is has improved: bugs in the software may have been
fixed, but new ones will appear, and most importantly, the security
management policy at ISC is still the same: security holes will be