2

To add 3rd party plugins in Xcode, one should create their own certificate and to sign Xcode with it. But self-signed certificates expire after 1 year. How can I make specific code to be executed every year? Probably there's a way, but then I have another problem -- is there a way to create certificates with terminal, not through Keychain Access app?

Also is it unsafe? I don't see any difference between manual certificate creation and automatic, so if it is unsafe, then creating such certificates is overall unsafe.

1

Yes, you can use command line tools to issue your own self-signed certificates. These need not be limited to one year.

There is no difference between Keychain Access created certificates and those you create using command line tools.

openssl

With openssl you can create certificates of any duration. The question and answers for how to create a self-signed certificate with OpenSSL will get you started. The command is effectively:

openssl req -x509 -newkey rsa:4096 -keyout key.pem -out cert.pem -days 730

The command above will result in a two year self-signed certificate.

Automatic versus Manual

Regarding safety, there is no difference in safety between certificates created by Keychain Access's graphical interface and those by command line tools.

The safety of self-signed certificates can be an issue. Self-signed certificates are not signed by a trusted third party. This third party signature typically only matters when the certificate is being used outside of your immediate environment – which it is not for this situation.

Ad-Hoc

You can also ad-hoc codesign an application without a certificate:

sudo codesign -f -s - /Applications/Xcode.app

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .