I am trying to install the signing keys which i have recieved from RIM.I have install them successfully on my workstation,but when i am trying to to sign my any cod file.it gives error
"Unable to Request signatures until this application has been registered with all signing authorities required"
i am not understanding which steps i have missed.please help me out.
Thanks,
Sagar.
you need to have 3 keys installed in your system. RIM provides 3 certificates. install all of them. same process followed to all of them. then restart eclipse or system if required. sure it will work.
Related
After completing all MAC development, only the deployment stage remains.
I'm a complete beginner developer on MAC.
But when I was deploying, the gatekeeper blocked me, and when I deployed I knew I had to build with a new provisioning file.
So I tried to make it on the Apple Developer site but all failed )-:
Please see below for the steps I followed
Generate a certificate on the MAC PC (.CSR)
Create a Developer ID Application certificate in the Certificates, Identifiers & Profiles screen (using the .CSR created in step 1)
After that, I went to Profile and selected the option to deploy using Developer ID and proceeded, but only the message that there is no certificate is displayed as shown below.
Does anyone know how to solve this problem?
Failure to create a provisioning profile using Developer ID when there is an actual certificate is an Apple problem, and the problem has been resolved in Apple Korea.
It took Apple about 3 weeks to solve the problem, and when I got a response and checked, it worked normally.
Any windows uwp "experts" here?
I've been researching on the below mentioned topic for a day now as I couldn't believe there is no way that we can distribute our UWP App.
Is it really not possible to distribute an UWP App through a different channel than the store without having to manually run+interact with the powershell script?
Because we can't really do that for our customers everytime. They also do not have admin rights and are not allowed to use the normal windows store.
Just installing the certificate and then running the appxbundle does not work, we always have to run the powershell script in order for it to work... :/
UWP-apps that are not from the store need to signed with a trusted certificate. Otherwise the installation will not be successful.
If your app is correctly signed and the certificate is trusted, you can double-click the .appxbundle to install the app on more recent versions of Windows 10.
The powershell script only needs admin rights because it adds the temporary developer-certificate to your trusted certificates.
First off you need to create a certificate and sign your appx/appxbundle with that.
You have have to install the Certificate on your Clients Machine but for that you need Admin rights.
So you have to give your client the certificate and they have to distribute it via Group Policies.
That way you don't have to install the certificate via the powershell script.
Now you can write a script that will install the Dependencies and Appx on the Machine. For that you don't need admin rights, but side loading must be activated. But like I said the Certificate has to. be installed otherwise you can't not install the App.
I need to upload an app on the account of a client. I logged in with xcode but I can't select the IOS distribution code signing profile, I tried to download the IOS distribution certificate from their member center
But even if I download it and double click in order to install it on the keychain I cannot use it.. Should I create a new IOS distribution certificate or is there a workaround?
I'm not 100% sure. I think you need to have their developer profile installed on your computer. It will want you to export the profile from the keychain on their Mac and you would install on yours. If they only have an account but do not use it for anything other than to sell their app you might be in a better position to just set it up on yours. If they do have it installed then it can be a bit tricky. I don't expect this to be an answer but I hope it helps you find the solution.
Good luck!
You cannot use it, because private key should exist at your machine for this certificate, you cannot download it from anywhere except the export process from machine for which it was generated. In your case request new certificate for your machine.
I've done codesigning and submitting for iOS apps countless times. This time it struck me with the Mac App Store. I'm repeatedly getting the same error message:
"My Name" is a valid identity. However,
you do not have the associated package identity.
I've recognized this 2 topics here on stack overflow:
mas-code-signing-identity-private-key and mac-app-package-identity-not-installed
Nothing inside there solved the problem for me.
Thats how I (most reliably) reproduce this message:
I clean up all my certificates and private keys starting with "Mac Developer" or "3rd Party Mac Developer". Of course also the expired ones.
Revoking all the stuff inside the Mac certification portal.
Create App-ID (did it only once)
Create new certificate for Mac Development. I can only assume that this is comparable to the debugging certificates for iOS development.
Create new certificate for Mac App. Once again I can only assume that this could be something similar to a distribution certificate in iOS-development.
For completion reasons create a new certificate/profile for my system.
Create a production provisioning profile. I can only assume that this might be equivalent to an iOS distribution profile.
I then download all the certificate mess and install it properly. Some go into the Keychain, others got into the Preferences and XCode.
For making sure I restart XCode or even the whole Mac (doesn't change the frustrating outcome anyway).
I go to the project build settings and select the production provisioning profile, because I assume "production" is equivalent to "distribution". Changing the codesigning identity in the target build settings doesn't work either. While Apple claims in it's documentation that for App Store submission the signing identity has to be changed in the project build settings.
I run an archive build.
I select the archive in the organizer and click validate.
This error message appears:
"My Name" is a valid identity. However,
you do not have the associated package identity.
I can't find any pointer to what the term "package identity" actually means. What is most frustrating to me is that this terminology mess in Apples documentation concerning the code signing and submission process appears not very clear and precise to me. At least not as clear and precise as the documentation for the same process concerning iOS App submission (which is using completely different terminology).
Probably I understood something wrong? Thanx for any help or pointer in advance.
OK, I have some important pointers (additional to Apples documentation) for people stumbling over similar issues.
The error message is totally misleading.
Don't take every word in Apples documentation too seriously.
For solving the issue, 2 points have been most significant:
Additional to all the other profile-mess you need 2 certificates for submission to the Mac App Store (contrary to the same process for iOS App Store submission). Both have to be installed together with their corresponding public and private key pairs.
Mac App
Mac Installer
The codesigning needs to be set on the build target, not the project. I don't remember where but this was described wrong side around in one of Apples documentations.
Eventually my submission worked by keeping to those 2 points.
There is an additional issue with Keychain & XCode.
When Xcode uses a certificate, they want one and only one certificate in your keychain. If you have an expired one, as well as a valid one, Xcode often fails the operation.
So you look at your keychain using Keychain Access, and do not see an expired certificate. It is still there! The default setting for Keychain Access hides expired certificates. Goto the View menu and select Show Expired Certificates. Delete all the expired ones, they are not good for anything.
Quit Keychain Acces and Relaunch Xcode. Xcode often requires a relaunch when adding/deleting certificates.
At that point, the Archive Validate process worked for me.
This is what it was for me as well.
Just want to clarify, you absolutely need both Mac App Distribution and Mac Installer Distribution certificates. Thanks Jacque for your explanation above. It should look like this:
Yes the problem is Mac Installer Distribution certificate.
The easiest way to have everything fixed and loose all the troubles just go to Xcode->Window->Organizer->Devices and then on the lower right corner press on Refresh and log in with your account... xcode will generate and download all the certificates and provisioning profiles needed.
I have made an application for Windows & everytime I run the application by opening the executable file I get the "Publisher Unverified" warning in Windows. It is fine if I was the only audience for this app but thats not the case. Is there any way to program my app such that this message does not show up for the users.
The only way to do this is to obtain and use a code signing certificate from a trusted source. Microsoft calls this Authenticode.
Unfortunately for the little guy, these cost. Verisign sells theirs for about four hundie a year.
Here are some starting points you should read about Authenticode:
http://msdn.microsoft.com/en-us/library/ms537359(VS.85).aspx
http://technet.microsoft.com/en-us/library/cc750035.aspx
http://msdn.microsoft.com/en-us/library/aa379872(VS.85).aspx
Some certificate dealers:
http://www.verisign.com
http://www.thawte.com
http://www.globalsign.net
http://www.geotrust.com
For a cheaper code signing certificate, you can use Comodo. There is a reseller called KSoftware which sells their certificates for $99/yr:
http://www.ksoftware.net/code_signing.html
I used them a few years ago and had no problems.
You can then use SignTool from the .net SDK to sign your EXE files. There is a tutorial here:
http://www.tech-pro.net/code-signing-for-developers.html
I think there is a way to resolve this. We need to add digital signature to the executables. The way to add digital signatures is very nicely outlined at,
http://blog.didierstevens.com/2008/12/30/howto-make-your-own-cert-with-openssl/
http://blog.didierstevens.com/2008/12/31/howto-add-a-digital-signature-to-executables/
Basically we will use OpenSSL to create our own digital signatures and then use the SignTool application by Microsoft to add it to our executable.