A file extension is the set of three or four characters at the end of a filename; in this case,.pks. File extensions tell you what type of file it is, and tell Windows what programs can open it. Windows often associates a default program to each file extension, so that when you double-click the file, the program launches automatically. The 1st step prompts you for the password to open the PFX. The 2nd step prompts you for that plus also to make up a passphrase for the key. The 3rd step prompts you to enter the passphrase you just made up to store decrypted. The 4th puts it all together into 1 file. You need to rename.pem to.cer first in order for Windows to recognize the file as a certificate/private key file. Both file extensions may contain cert(s) and/or key(s) in either ASCII-armored plaintext or Base64/DER encoded binary format, but you can use cer files with Windows built-in utilities. On the Linux VM you want to use to register the key, create a file named pks-nsx-t-superuser.key. Copy the generated private key into the file. Copy the generated private key into the file. Save both files.
HTTPS requires an SSL Certificate. When you generate an SSL Certificate,you are creating a keystore file and a keystore password for use when the browser interface connectsto the Master Server.
You can choose whether to have a Certifying Authority sign the certificateor you can use a self-signed certificate. A certificate signed by a CertifyingAuthority is trusted by browsers, therefore the browser does not issue a warningwhen a user connects to the browser interface on the Master Server. Generally, CertifyingAuthorities charge a fee to sign a certificate. A self-signed certificateis available for use immediately after you generate the certificate becauseyou do not have to wait for the Certifying Authority to sign it. However,a self-signed certificate is not trusted by the browser, so the browser issuesa warning each time a user connects to the Master Server.
To enable the browser interface to use SSL, you must first generate an SSL Certificate.You create a keystore file and a keystore password while you generate an SSLCertificate.
To create a keystore file and a keystore password you will use keytool. keytool is a security tool availablewith the JRE. If you do not have keytool installed, youmust install keytool before you can configure the provisioningsystem to use HTTPS. The N1 Service Provisioning System installs the JRE. If you are configuringHTTPS after you have installed the provisioning system, keytool isinstalled on the system.
Change to the directory in which you installed the JRE.
JAVA-HOME is the directory where you installedthe JRE. If you installed the JRE with the N1 Service Provisioning System 5.1, the JRE is installedin the N1SPS5.1-home/common/jre/bin directory.
Generate the certificate.
Set /keystore-location to the location andfilename of the keystore file where you want to store the generated key.
Set password to whatever passwordthat you want to use as the keystore password.
Follow the prompts to complete.
Do not include anypunctuation in the name of your organization, otherwise the Java Certificatetool fails when attempting to generate the request. The Common Name (CN)must be set to the fully qualified host name, including the domain name, componentof the URI.
If you want to use a Certificate signed by a Certifying Authority, followthis procedure to submit the Certificate to the Certifying Authority to besigned.
Generate the Certificate Request.
/keystore-location is the location and filenamewhere you stored the generated key.
Send the Certificate Request to the Certifying Authority.
Follow the instructions provided by the Certifying Authority. The CertifyingAuthority returns a Certificate Reply.
Save the Certificate Reply to a file.
Verify the Certificate Reply.
certificate-reply-file is the filename ofthe Certificate Reply that you received from the Certifying Authority.
Import the Certificate Reply file to the keystore file.
/keystore-location is the location and filenamewhere you stored the generated key. certificate-reply-file isthe filename of the Certificate Reply that you received from the CertifyingAuthority.
Verify the imported Certificate Reply.
/keystore-location is the location and filenamewhere you stored the generated key.
The Strong Name tool (Sn.exe) helps sign assemblies with strong names. Sn.exe provides options for key management, signature generation, and signature verification.
Warning
Do not rely on strong names for security. They provide a unique identity only.
For more information on strong naming and strong-named assemblies, see Strong-Named Assemblies and How to: Sign an Assembly with a Strong Name.
The Strong Name tool is automatically installed with Visual Studio. To start the tool, use the Developer Command Prompt (or the Visual Studio Command Prompt in Windows 7). For more information, see Command Prompts.
Note
On 64-bit computers, run the 32-bit version of Sn.exe by using the Developer Command Prompt for Visual Studio and the 64-bit version by using the Visual Studio x64 Win64 Command Prompt.
At the command prompt, type the following:
| Option | Description |
|---|---|
-a identityKeyPairFile signaturePublicKeyFile | Generates AssemblySignatureKeyAttribute data to migrate the identity key to the signature key from a file. |
-ac identityPublicKeyFile identityKeyPairContainer signaturePublicKeyFile | Generates AssemblySignatureKeyAttribute data to migrate the identity key to the signature key from a key container. |
-c [csp] | Sets the default cryptographic service provider (CSP) to use for strong name signing. This setting applies to the entire computer. If you do not specify a CSP name, Sn.exe clears the current setting. |
-d container | Deletes the specified key container from the strong name CSP. |
-D assembly1 assembly2 | Verifies that two assemblies differ only by signature. This is often used as a check after an assembly has been re-signed with a different key pair. |
-e assembly outfile | Extracts the public key from assembly and stores it in outfile. |
-h | Displays command syntax and options for the tool. |
-i infile container | Installs the key pair from infile in the specified key container. The key container resides in the strong name CSP. |
-k [keysize] outfile | Generates a new RSACryptoServiceProvider key of the specified size and writes it to the specified file. Both a public and private key are written to the file. If you do not specify a key size, a 1,024-bit key is generated by default if you have the Microsoft enhanced cryptographic provider installed; otherwise, a 512-bit key is generated. The keysize parameter supports key lengths from 384 bits to 16,384 bits in increments of 8 bits if you have the Microsoft enhanced cryptographic provider installed. It supports key lengths from 384 bits to 512 bits in increments of 8 bits if you have the Microsoft base cryptographic provider installed. |
-m [y n] | Specifies whether key containers are computer-specific, or user-specific. If you specify y, key containers are computer-specific. If you specify n, key containers are user-specific. If neither y nor n is specified, this option displays the current setting. |
-o infile [outfile] | Extracts the public key from the infile and stores it in a .csv file. A comma separates each byte of the public key. This format is useful for hard-coding references to keys as initialized arrays in source code. If you do not specify an outfile, this option places the output on the Clipboard. Note: This option does not verify that the input is only a public key. If the infile contains a key pair with a private key, the private key is also extracted. |
-p infile outfile [hashalg] | Extracts the public key from the key pair in infile and stores it in outfile, optionally using the RSA algorithm specified by hashalg. This public key can be used to delay-sign an assembly using the /delaysign+ and /keyfile options of the Assembly Linker (Al.exe). When an assembly is delay-signed, only the public key is set at compile time and space is reserved in the file for the signature to be added later, when the private key is known. |
-pc container outfile [hashalg] | Extracts the public key from the key pair in container and stores it in outfile. If you use the hashalg option, the RSA algorithm is used to extract the public key. |
-Pb [y n] | Specifies whether the strong-name bypass policy is enforced. If you specify y, strong names for full-trust assemblies are not validated when loaded into a full-trust AppDomain. If you specify n, strong names are validated for correctness, but not for a specific strong name. The StrongNameIdentityPermission has no effect on full-trust assemblies. You must perform your own check for a strong name match. If neither y nor n is specified, this option displays the current setting. The default is y. Note: On 64-bit computers, you must set this parameter in both the 32-bit and the 64-bit instances of Sn.exe. |
-q[uiet] | Specifies quiet mode; suppresses the display of success messages. |
-R[a] assembly infile | Re-signs a previously signed or delay-signed assembly with the key pair in infile. If -Ra is used, hashes are recomputed for all files in the assembly. |
-Rc[a] assembly container | Re-signs a previously signed or delay-signed assembly with the key pair in container. If -Rca is used, hashes are recomputed for all files in the assembly. |
-Rh assembly | Recomputes hashes for all files in the assembly. |
-t[p] infile | Displays the token for the public key stored in infile. The contents of infile must be a public key previously generated from a key pair file using -p. Do not use the -t[p] option to extract the token directly from a key pair file. Sn.exe computes the token by using a hash function from the public key. To save space, the common language runtime stores public key tokens in the manifest as part of a reference to another assembly when it records a dependency to an assembly that has a strong name. The -tp option displays the public key in addition to the token. If the AssemblySignatureKeyAttribute attribute has been applied to the assembly, the token is for the identity key, and the name of the hash algorithm and the identity key is displayed. Note that this option does not verify the assembly signature and should not be used to make trust decisions. This option only displays the raw public key token data. |
-T[p] assembly | Displays the public key token for assembly. The assembly must be the name of a file that contains an assembly manifest. Sn.exe computes the token by using a hash function from the public key. To save space, the runtime stores public key tokens in the manifest as part of a reference to another assembly when it records a dependency to an assembly that has a strong name. The -Tp option displays the public key in addition to the token. If the AssemblySignatureKeyAttribute attribute has been applied to the assembly, the token is for the identity key, and the name of the hash algorithm and the identity key is displayed. Note that this option does not verify the assembly signature and should not be used to make trust decisions. This option only displays the raw public key token data. |
-TS assembly infile | Test-signs the signed or partially signed assembly with the key pair in infile. |
-TSc assembly container | Test-signs the signed or partially signed assembly with the key pair in the key container container. |
-v assembly | Verifies the strong name in assembly, where assembly is the name of a file that contains an assembly manifest. |
-vf assembly | Verifies the strong name in assembly. Unlike the -v option, -vf forces verification even if it is disabled using the -Vr option. |
-Vk regfile.reg assembly [userlist] [infile] | Creates a registration entries (.reg) file you can use to register the specified assembly for verification skipping. The rules for assembly naming that apply to the -Vr option apply to –Vk as well. For information about the userlist and infile options, see the –Vr option. |
-Vl | Lists current settings for strong-name verification on this computer. |
-Vr assembly [userlist] [infile] | Registers assembly for verification skipping. Optionally, you can specify a comma-separated list of user names the skip verification should apply to. If you specify infile, verification remains enabled, but the public key in infile is used in verification operations. You can specify assembly in the form *, strongname to register all assemblies with the specified strong name. For strongname, specify the string of hexadecimal digits representing the tokenized form of the public key. See the -t and -T options to display the public key token. Caution: Use this option only during development. Adding an assembly to the skip verification list creates a security vulnerability. A malicious assembly could use the fully specified assembly name (assembly name, version, culture, and public key token) of the assembly added to the skip verification list to fake its identity. This would allow the malicious assembly to also skip verification. |
-Vu assembly | Unregisters assembly for verification skipping. The same rules for assembly naming that apply to -Vr apply to -Vu. |
-Vx | Removes all verification-skipping entries. |
-? | Displays command syntax and options for the tool. |
Note
All Sn.exe options are case-sensitive and must be typed exactly as shown to be recognized by the tool.
The -R and –Rc options are useful with assemblies that have been delay-signed. In this scenario, only the public key has been set at compile time and signing is performed later, when the private key is known.
Note
For parameters (for example, –Vr) that write to protected resources such as the registry, run SN.exe as an administrator.
The Strong Name tool assumes that public/private key pairs are generated with the AT_SIGNATURE algorithm identifier. Public/private key pairs generated with the AT_KEYEXCHANGE algorithm generate an error.
The following command creates a new, random key pair and stores it in keyPair.snk.
The following command stores the key in keyPair.snk in the container MyContainer in the strong name CSP.
The following command extracts the public key from keyPair.snk and stores it in publicKey.snk. /age-of-empires-3-the-warchiefs-cd-key-generator.html.
The following command displays the public key and the token for the public key contained in publicKey.snk.
/jira-cloud-generate-api-key.html. The following command verifies the assembly MyAsm.dll.
The following command deletes MyContainer from the default CSP.