> What’s to deal with? It’s still the same as before: not secure.
But there is no meaningful way to make it secure. So marking it not secure creates just noise.
But there is no meaningful way to make it secure. So marking it not secure creates just noise.
It's informative: you might not be able to do anything about it, but you should know it anyway.
If the same thing happens in my local lan I don't want the same warning, because if I get the same warning I will start to ignore it, and not only when I'm in my local lan.