This might be via an app or IO event like a USB devices being plugged in. The intervention should be triggered automatically, when the system is requested to load the extension. Apps need to have a simple way to trigger an intervention that is the same for all apps, so users have to train about this only once. What I would suggest is a more open way of giving the users an easy way to review this. Some KEXTs disabled as a result will not be requested to be loaded until days later. Techno speak will not make the situation more secure.ģ. Users do not have the foggiest, what KEXTs are - and they should not have to know. Users do not read dialogs, they often click out of them.Ģ. But the whole user experience needs to be reviewed.ġ. I fully understand the reasoning behind tightenig the security policy.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |