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.
-
-
I think what Matt is getting at is the Enterprise use case. The Enterprise owns the computer, but the issue of privacy is not as clear-cut, including in situations where technically you have pre-authorization.
-
I don't follow, as you said, the enterprise owns the computer and therefore is the owner. They have authorization, which is another word for permission, no issue from me, you're all good.
- 16 more replies
New conversation -
-
-
This is similar to "one party consent" vs "two party consent" vs "multi party consent" paradigms for voice calling. Except in DNS there's no easy way to obtain caller consent for the call to be recorded.
-
I mean, it's obvious someone NOT PARTY AT ALL to a data conversation (e.g, the ISP) has no default consent in the transaction so I'm not derailing that piece. But it's simplistic to talk about a DNS query in terms of "the owner" when there can be many parties generating content.
- 2 more replies
New conversation -
-
-
You obviously need permission to say who the owner is
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.