If you want to snoop on DNS queries, you should get permission from the owner. Period. The mental gymnastics to rationalize not needing permission, or claim that isn't the issue have been quite impressive.
The fact that you're complicating it so much is making me worry what you want to justify? Give me a real example.
-
-
Seems like a real example to me. Is this performance art?
-
Yeah, I thought I had given a real example. Also, accusing me of "wanting to justify something" is pretty unfriendly here. I'm interested in knowing how you think about this problem. I think about it from an enterprise defense framework, where ownership is a complicated thing.
- 3 more replies
New conversation -
-
-
It is as simple as it were since the release of DNS. The server is entitled to log the request it answers. the user can choose which server it will use, knowing that server may log it. Snoop, and the need for authorization, is anything in the middle exploit the clear text nature.
-
Authorization, as in concent. Of course, malicious actors will just do it. And thats the same as were in HTTP times. DoH will solve that problem. If the server will log, thats expected behavior, as always were. If that server will share or use that log for something else...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Don't worry, you cannot have too much permission to snoop.