summaryrefslogtreecommitdiffstats
path: root/e-post
diff options
context:
space:
mode:
authorGuilhem Moulin <guilhem@fripost.org>2022-12-13 17:52:28 +0100
committerGuilhem Moulin <guilhem@fripost.org>2022-12-13 17:52:28 +0100
commit38fb7adba38b668fd62b1eb8fe92cec4b5974035 (patch)
tree60768b2cd9162528ba20c2a04e9c319836b36273 /e-post
parentd65ed1731a55c19b90709a8baa356284640b5c7d (diff)
Remove note that Fripost doesn't use DNSSEC.
Our zone has been authenticated since mid September 2021.
Diffstat (limited to 'e-post')
-rw-r--r--e-post/doman.mdwn7
1 files changed, 3 insertions, 4 deletions
diff --git a/e-post/doman.mdwn b/e-post/doman.mdwn
index 4c153db..c20a76c 100644
--- a/e-post/doman.mdwn
+++ b/e-post/doman.mdwn
@@ -275,10 +275,9 @@ Here `example.org` is merely copying Fripost's policy.
Here the policy says that mails `@example.org` should PASS if they're
being accepted by Fripost's policy, that is if the sender host is
`outgoing.fripost.org` and FAIL otherwise (where Fripost's policy would
-return NEUTRAL). Note however that DNS is spoofable, and as
-unfortunately Fripost doesn't use DNSSEC at the moment, an attacker
-could for instance poison the DNS cache and fake the reply for
-`outgoing.fripost.org`'s TXT record.
+return NEUTRAL). Note however that DNS is spoofable, and if the
+`example.org` zone isn't authenticated then an attacker could poison the
+DNS cache resulting in a malicious SPF policy.
example.org IN TXT "v=spf1 a include:outgoing.fripost.org -all"