As I'm fairly sure I described in detail before, base32 provides the
option of reversing the encoding at the server, looking up the local
part using whatever fuzzy matching the server wants to use, and
sending an appropriate response.
This pretends that the server can read the human mind of the sender.
No, it does not. Gratuitous insults like this are not helpful.
It's an equally insecure fuzzy matching logic, but now done at the
server side instead of the client side. How is [email protected] going
to get matched by this server side? To me? to Paul Hoffman? To no one?
Hmmn. The assumptions in this paragraph are a bit much.
Having actually written mail servers, and written books about mail
servers, and written a few stunt DNS servers, based on my personal
experience it would not be unreasonably difficult to adapt a DNS server to
use the mail server's address matching logic to find the account to which
a local part actually corresponds so it can get the PGP (or whatever) key
that goes with that account. There's nothing insecure about this, it's
resolving the local part according to RFC 5321, the same way a mail server
does. In your example, it's matched to whatever internal account
[email protected] corresponds to.
Yeah, it requires the DNS server and mail server to talk to each other, or
at least share a database, but that's the price you have to pay if you
want to force SMTP features into the DNS.
If you're saying you can't imagine how someone could do this, I won't
argue but it doesn't impress me as a very good basis for protocol design.
Regards,
John Levine, [email protected], Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
_______________________________________________
dane mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dane
