6 ms·
I agree with this in general. In specific though: > We can't stop the middlebox from saying well, Bob publishes a trans rights blog so now all Bob's blogs are
by delusional 1y ago
I agree with this in general. In specific though:
> We can't stop the middlebox from saying well, Bob publishes a trans rights blog so now all Bob's blogs are inaccessible just in case.
Seems incorrect. Bob could publish a single key without any indication of what is behind that key. Alice would get that key (from DNS), but since it was just for talking with Bob in general, nobody knows what Bob has. Alice and Bob are then free to talk about their trans rights.
The particular point is that there's no reason the middlebox would even know there is a subdomain called trans-rights.bob.example.
- tialaramex 1y agoThere are great number of ways in which the operators of the middlebox might come to know that Bob publishes this blog. Most obviously the humans charged with setting up such tech might literally find out in the ordinary course of their life that they ought to add this rule. Fox News show headline "Ban this sick filth", a letter from the Government about "Extremist sites unsuitable for your employees", and so on. But technologically there could be a list, maybe a "Ministry of Truth" provides the list of providers who are forbidden, it needn't say why, and if it does say it could lie, usually such lists are (like spam blackholing) automated and unsupervised. They could search the "Passive DNS" system to find suspicious names and block the entire provider, or likewise with Certificate Transparency. So alas there are reasons the middlebox might be configured this way.