Traffic Shaping Refactor First Pass

This commit is contained in:
Mike Hillyer
2026-06-09 13:23:56 -04:00
parent 4eedf9361e
commit 164f109326
18 changed files with 544 additions and 515 deletions
+1 -1
View File
@@ -116,7 +116,7 @@ There are three main ways in which you can manage that risk:
ensure that the TLS is set to required even if your default policy is
opportunistic.
* For well-known sites with working TLS, such as Google, override the
opportunistic TLS with required TLS in your [shaping configuration](../configuration/trafficshaping.md).
opportunistic TLS with required TLS in your [shaping configuration](../trafficshaping/shapingfiles.md).
* Consider enabling [DANE](../../reference/kumo/make_egress_path/enable_dane.md), which is
similar in effect to MTA-STS, using signed DNS records instead of publishing
its policy via HTTPS. It requires working and trusted DNSSEC