> On May 21, 2016, at 4:33 PM, Rainer Müller <[email protected]> wrote: > > On 05/21/2016 04:33 PM, René J.V. Bertin wrote: >> ..., >> wouldn't it be possible to design an interface that allows users to specify >> an identity in macports.conf, and ports to invoke codesign in the >> post-activate stage? > > Yes, of course. This would be the way to implement code-signing. When > previously > discussed, the suggestion was to generate a local identity automatically. > > Although I am not aware of a method to automatically generate and import a > certificate into the System keychain for code signing except using the > Certificate Assistant in Keychain Access.app. > > For the details of code-signing, see these instructions for example: > https://sourceware.org/gdb/wiki/BuildingOnDarwin
OpenSSL might be able to accomplish the same task and it is possible with OpenSSL to write a config file that fills in all the required fields. Port could write such a config per user. https://developer.apple.com/library/mac/technotes/tn2206/_index.html Regards, Bradley Giesbrecht (pixilla) _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
