Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

self-signed codesigning certificate? (mac) #458

Closed
ghost opened this issue Jun 2, 2016 · 9 comments · May be fixed by qcif/data-curator#563
Closed

self-signed codesigning certificate? (mac) #458

ghost opened this issue Jun 2, 2016 · 9 comments · May be fixed by qcif/data-curator#563

Comments

@ghost
Copy link

ghost commented Jun 2, 2016

I created a certificate via keychain access > certificate assistant > create a certificate. (in the login keychain)

name: My Test Certificate
identity type: self signed root
certificate type: code signing

Then I type the following in the terminal before building;

export CSC_NAME="My Test Certificate"
But output is:

Identity name "My Test Certificate" is specified, but no valid identity with this name in the keychain

What is the problem? Is it not possible to use a self-signed certificate?

@develar
Copy link
Member

develar commented Jun 2, 2016

What is the problem? Is it not possible to use a self-signed certificate?

In our tests we use self-signed cert too. But it is supported only if you specify CSC_LINK and CSC_PASSWORD.

CSC_NAME doesn't support self-signed or non-Apple certs. Should be fixed.

@develar
Copy link
Member

develar commented Jun 4, 2016

Please try to make your self-signed cert as trusted using keychain (it must be green). Otherwise it is not valid and, so, not returned.

@Vj3k0
Copy link

Vj3k0 commented Jun 5, 2016

Hey Vladimir, doesn't work for me either. Same problem. I've created code signing certificate from Keychain Access. In release notes, I've seen:

CSC_NAME env or build.osx.identity is still not removed because it is required if you have several identities. But now instead of Developer ID Installer: Your Name (XXXXXXXXXX), you should specify only Your Name — appropriate certificate will be chosen automatically.

Can this be an issue?

@develar
Copy link
Member

develar commented Jun 6, 2016

@Vj3k0 Yes, should be fixed.

@develar
Copy link
Member

develar commented Jun 6, 2016

develar-home-imac:onshape-desktop-shell develar$ security find-identity -v -p codesigning
  1) 5160729A078E4EF0401986C2328E4D3BD55FFE0E "Test Test"
  2) 32F67D8F957E740C692ADD8CD5A5E463992193DD "Vladimir Krivosheev"
     2 valid identities found

screen shot 2016-06-06 at 20 25 56

@develar develar closed this as completed in 97e16a2 Jun 6, 2016
@antoniobrandao
Copy link

@develar that solved it, thanks ! ❤️

@gmcdev
Copy link

gmcdev commented Jun 16, 2016

@develar - THANK YOU!

@LckySndays
Copy link

LckySndays commented Oct 29, 2016

Anyone know how to use Mac Developer: XXX (YYYY) to sign?
Always got "is specified, but no valid identity with this name in the keychain" error
The certificate is exist in the keychain (security find-identity -v -p codesigning)

If I create my own certificate and make it trusted so it appear on (security find-identity -v -p codesigning), I can sign my Apps without any problem.

The problem only exist when using Mac Developer: XXX (YYYY) to sign the app
I have tried to just specify XXX or Mac Developer: XXX in CSC_NAME but still no luck.

Update:
Ok, I think i know it now
#812

@develar
Copy link
Member

develar commented Oct 29, 2016

@LckySndays It is forbidden currently, please vote for #812

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants