most people simply don't have the know-how to get that deep in the weeds
...Which is why the advice about DoH set off alarm bells. "Just copy and paste this example JSON file and put it in the right place and boom! you have configured DoH!" and I look at the JSON and it does not configure DoH at all but rather turns it off? And I think turning it off is LESS secure? Seemed like they did not expect people to get that deep into the weeds and actually read the JSON.
In a security context the second you catch someone in a lie or trying to mislead is the moment that they loose ALL credibility.
> most people simply don't have the know-how to get that deep in the weeds
...Which is why the advice about DoH set off alarm bells. "Just copy and paste this example JSON file and put it in the right place and boom! you have configured DoH!" and I look at the JSON and it does not configure DoH at all but rather turns it off? And I think turning it off is LESS secure? Seemed like they did not expect people to get that deep into the weeds and actually read the JSON.
In a security context the second you catch someone in a lie or trying to mislead is the moment that they loose ALL credibility.
(post is archived)