3 ms·
If you honestly can’t think of one, that only demonstrates your lack of imagination. I, for one, would imagine something based on a DNS TXT records that either
by pwdisswordfish2 7y ago
If you honestly can’t think of one, that only demonstrates your lack of imagination.
I, for one, would imagine something based on a DNS TXT records that either directly contain or point to a URL describing some kind of security domain policy: whether and which subdomains and subdirectories should be considered separate, isolated security domains, with pattern matching, of course. Or maybe put it under /.well-known/ instead of DNS. At the very least, this would solve the unregistration problem of PSL (i.e. when an entry becomes stale, you will not immediately know it, and old versions of your product will still treat it as present).
- wutwutwutwut 7y agoUsing DNS TXT to solve a XSS issue? That's clearly another card added to the house.
- yoloClin 7y agoIMO, using DNS for anything other than hostname lookups is a complete hack. I'm looking at you, SPF.
- pbhjpbhj 7y agoIt's a reasonable hack though. Where else do you put "how to interact with this domain" data, you can't serve that data (eg via http) because clients need to already know how to interact with that domain before they interact with that domain? How would you do it?
- yoloClin 7y agoTransport encryption with PKI.