Authenticode or other code signing for Mac and Linux

此生再无相见时 提交于 2019-12-05 20:10:07

The standard way of authenticating code running on a Linux system is to validate the binaries once while installing the package rather than every time they are run. The package (e.g. RPM) contains a cryptographic signature that must match the contents of the files or the installer will refuse to install. Standard UNIX permissions prevent ordinary users from modifying those files on disk afterward. Periodically, the checksums of the files on disk can be compared with what they should be (using RPM or TripWire or something similar) just in case they were able to be modified or become corrupted.

On the Mac you can sign your binaries with the same Authenticode cert you would use on Windows (at least we do this and it works fine).

You need to import the certificate (including the private key) into your keychain and then use Xcode or codesign to sign the binary.

标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!