It's also formulated in a way that clearly implicates "this is bad, don't do that!".
The warning makes sense if shown as part of a shortlived debug session to a developer. However, this is caused by a program that a non-technical user has installed permanently on the device.
So I'm confused how legitimate TLS inspection is supposed to work for this user group.
The warning makes sense if shown as part of a shortlived debug session to a developer. However, this is caused by a program that a non-technical user has installed permanently on the device.
So I'm confused how legitimate TLS inspection is supposed to work for this user group.