signing

问题 Within my Visual Studio solution I have a web site and 4-5 class library projects which are referenced., some of which reference external third party assemblies as well. I've been given the task of signing the assemblies for these projects. My understanding is that the purpose of signing is that not everyone being able to use our assembly without providing its public key and version details, right? Should I use one single Strong Name Key (.snk) to sign all the assemblies of these projects or

问题 We recently purchased an EV Code Signing Certificate . I followed instructions and I can successfully sign our built applications (exe files) , our libraries (dll) . However, I can't sign our setup packages (MSI files) , I always get this error: SignTool Error: An unexpected internal error has occurred. Error information: "Error: SignerSign() failed." (-2147024885/0x8007000b) I don't see anything in Event Viewer. I am really stuck here, I don't not understand how same command could work for

问题 I inherited some code using the deprecated bouncycastle API. Before updating it to the new API I wanted to write a test to verify that I didn't change its behaviour. However, I cannot work out the correct way to verify this signature that is generated. The code to be changed is: public static byte[] createSignedData(byte[] content, X509Certificate cert, PrivateKey key) throws NoSuchAlgorithmException, NoSuchProviderException, CMSException, IOException { // set up the generator

问题 I inherited some code using the deprecated bouncycastle API. Before updating it to the new API I wanted to write a test to verify that I didn't change its behaviour. However, I cannot work out the correct way to verify this signature that is generated. The code to be changed is: public static byte[] createSignedData(byte[] content, X509Certificate cert, PrivateKey key) throws NoSuchAlgorithmException, NoSuchProviderException, CMSException, IOException { // set up the generator

问题 I am attempting to create a PowerShell script that will: Build a message Sign the message using my private S/MIME certificate Encrypt the message using the S/MIME public cert of the recipient Send the email that has been signed and encrypted I have included the full script below but changed email addresses, cert names, etc. The private cert has been imported onto the machine using Internet Explorer. It is then referenced within the directory C:\Users\xxx\AppData\Roaming\Microsoft

问题 I am attempting to create a PowerShell script that will: Build a message Sign the message using my private S/MIME certificate Encrypt the message using the S/MIME public cert of the recipient Send the email that has been signed and encrypted I have included the full script below but changed email addresses, cert names, etc. The private cert has been imported onto the machine using Internet Explorer. It is then referenced within the directory C:\Users\xxx\AppData\Roaming\Microsoft

问题 I'm signing app using "Automatically manage signing". If I change "Build Configuration" to "Release" mode, What provisioning profile used for build an app? Release(Production) or Development? Is there anyway to check what provisioning profile (Development or Production) used for building app after app running? When I testing remote push notification, I set build configuration to "Release", could not receive any notification from server using production .p12 file. But when I downloaded app

问题 In PHP, I want to sign some documents with a padding of PSS, and a digest of SHA512. According to the docs, at http://www.php.net/manual/en/function.openssl-sign.php, I can set the digest however I need, by using a string, such as openssl_sign($text-to-sign,$binary_signature,$privkey,"sha512"); I don't see any way to set the padding, however. Can anyone please help me understand how I can sign text, using the RSA-PSS padding style, as seen in version 2.1 of PKCS #1? 回答1: In order not to be

问题 I have a simple question (maybe stupid) and i didn't find any clear answer to it. If i get a certificate from a trusted signing company (like verisign...) for one of my server (web for instance), i'll have private an public keys. With this certificate can i set up my own intermediate CA and sign cert request and the be trusted by every one (i know that's shouldn't be..)? My real question is : what will prevent me for issuing certificate and how the company can garanty that nobody does ??

问题 I have a simple question (maybe stupid) and i didn't find any clear answer to it. If i get a certificate from a trusted signing company (like verisign...) for one of my server (web for instance), i'll have private an public keys. With this certificate can i set up my own intermediate CA and sign cert request and the be trusted by every one (i know that's shouldn't be..)? My real question is : what will prevent me for issuing certificate and how the company can garanty that nobody does ??