For kernel maintainers, the idea is that these credentials would back the identities behind signed code: instead of relying solely on a PGP key signed at a conference years ago, maintainers could check a bundle of fresh credentials proving that the key they see belongs to the same person recognized by the Linux Foundation, their employer, or other trusted issuers. These credentials can be fed into transparency logs and other audit systems.
The trade-off is performance. Every syscall goes through user-space interception, which adds overhead. I/O-heavy workloads feel this the most. For short-lived code execution like scripts and tests, it is usually fine, but for sustained high-throughput I/O, it can matter.，这一点在快连下载安装中也有详细论述
-> [ anyRcv newKeywordPart: anyArg1 staticPart: anyArg2 ]，推荐阅读safew官方版本下载获取更多信息
Foreign Investment Surges to Canada’s Strongest Level Since 2007，这一点在下载安装 谷歌浏览器 开启极速安全的 上网之旅。中也有详细论述