7 Nokia Corporation - initial contribution. |
7 Nokia Corporation - initial contribution. |
8 Contributors: |
8 Contributors: |
9 --> |
9 --> |
10 <!DOCTYPE concept |
10 <!DOCTYPE concept |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
12 <concept id="GUID-2861F3D9-875E-5AB3-9600-B328F042CC38" xml:lang="en"><title>MakeKeys |
12 <concept id="GUID-2861F3D9-875E-5AB3-9600-B328F042CC38" xml:lang="en"><title>MakeKeys Overview</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 Overview</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
13 <p>The <xref href="GUID-557BF1DA-B6E8-521B-89F0-15C84E3BCB1A.dita">MakeKeys</xref> tool is a PC-side command-line tool that enables Symbian application |
14 <p>The <xref href="GUID-557BF1DA-B6E8-521B-89F0-15C84E3BCB1A.dita">MakeKeys</xref> tool |
14 developers to create a private key-public key pair and generate certificate |
15 is a PC-side command-line tool that enables Symbian application developers |
15 requests. </p> |
16 to create a private key-public key pair and generate certificate requests. </p> |
16 <section id="GUID-0640D79C-BFA7-4D39-AB00-DE4213CB5A66"><title>Purpose</title><p>The MakeKeys tool can be used to |
17 <section><title>Purpose</title><p>The MakeKeys tool can be used to create |
17 create a private key-public key (in form of a self-signed certificate) |
18 a private key-public key (in form of a self-signed certificate) pair. The |
18 pair. The private key can then be used by the <xref href="GUID-B20EE8A3-D7B2-5872-AF43-001A88C1A46E.dita">SignSIS</xref> tool |
19 private key can then be used by the <xref href="GUID-B20EE8A3-D7B2-5872-AF43-001A88C1A46E.dita">SignSIS</xref> tool |
19 to digitally sign an installation file. The self-signed certificate |
20 to digitally sign an installation file. The self-signed certificate can be |
20 can be used by the MakeKeys tool to create a certificate request file, |
21 used by the MakeKeys tool to create a certificate request file, which can |
21 which can then be submitted to a Certification Authority (CA) for |
22 then be submitted to a Certification Authority (CA) for signing. </p><note>The |
22 signing. </p><note>The MakeKeys tool cannot generate Certification |
23 MakeKeys tool cannot generate Certification Authority (CA) certificates.</note> </section> |
23 Authority (CA) certificates.</note> </section> |
24 <section><title>Key concepts and terms</title> <dl> |
24 <section id="GUID-0E7C093E-2B5C-4B44-9512-22F4B425630D"><title>Key concepts and terms</title> <dl> |
25 <dlentry> |
25 <dlentry> |
26 <dt>Key</dt> |
26 <dt>Key</dt> |
27 <dd><p>A key is a constant value applied using a cryptographic algorithm to |
27 <dd><p>A key is a constant value applied using a cryptographic algorithm |
28 encrypt text or to decrypt encrypted text. </p> <p>Keys are classified as |
28 to encrypt text or to decrypt encrypted text. </p> <p>Keys are classified |
29 symmetric and asymmetric based on the type of algorithm applied. If the same |
29 as symmetric and asymmetric based on the type of algorithm applied. |
30 key is used for both encryption and decryption, it is symmetric. If different |
30 If the same key is used for both encryption and decryption, it is |
31 keys are used for encryption and decryption, they are asymmetric. Asymmetric |
31 symmetric. If different keys are used for encryption and decryption, |
32 keys exist in the form of a private key-public key pair, where the public |
32 they are asymmetric. Asymmetric keys exist in the form of a private |
33 key is used for encryption and the private key is used for decryption. For |
33 key-public key pair, where the public key is used for encryption and |
34 more information, see <xref href="GUID-FB2CAA46-8EBB-5F76-847C-F3B953C9D31C.dita">Public |
34 the private key is used for decryption. For more information, see <xref href="GUID-FB2CAA46-8EBB-5F76-847C-F3B953C9D31C.dita">Public Key Cryptography</xref>. </p> </dd> |
35 Key Cryptography</xref>. </p> </dd> |
|
36 </dlentry> |
35 </dlentry> |
37 </dl> <dl> |
36 </dl> <dl> |
38 <dlentry> |
37 <dlentry id="GUID-D0BF05DB-046F-4E57-8FE1-A59412F56B69"> |
39 <dt>Certification Authority</dt> |
38 <dt>Certification Authority</dt> |
40 <dd><p>Certification Authority (CAs) is a trusted third party that provides |
39 <dd><p>Certification Authority (CAs) is a trusted third party that |
41 root certificates to users (End Entities). For details, see <xref href="GUID-911E9F7E-D0AD-55EC-A3F4-1D427F803780.dita">Certificates</xref>. </p> </dd> |
40 provides root certificates to users (End Entities). For details, see <xref href="GUID-911E9F7E-D0AD-55EC-A3F4-1D427F803780.dita">Certificates</xref>. </p> </dd> |
42 </dlentry> |
41 </dlentry> |
43 </dl> <dl> |
42 </dl> <dl> |
44 <dlentry> |
43 <dlentry> |
45 <dt>Digital signature</dt> |
44 <dt>Digital signature</dt> |
46 <dd><p>A digital signature is used to verify that a message (or data) actually |
45 <dd><p>A digital signature is used to verify that a message (or data) |
47 came from the sender (the one who signed the message) and that it has not |
46 actually came from the sender (the one who signed the message) and |
48 been tampered with. For details, see <xref href="GUID-5C58F7D1-D672-5B6D-AD48-863EC68F7446.dita">Digital |
47 that it has not been tampered with. For details, see <xref href="GUID-5C58F7D1-D672-5B6D-AD48-863EC68F7446.dita">Digital Signatures</xref>. </p> </dd> |
49 Signatures</xref>. </p> </dd> |
|
50 </dlentry> |
48 </dlentry> |
51 </dl> </section> |
49 </dl> </section> |
52 </conbody><related-links> |
50 </conbody><related-links> |
53 <link href="GUID-D45A4AE9-4169-4466-B02B-629B15C3E9AA.dita"><linktext>MakeKeys |
51 <link href="GUID-D45A4AE9-4169-4466-B02B-629B15C3E9AA.dita"><linktext>MakeKeys |
54 Tutorials</linktext></link> |
52 Tutorials</linktext></link> |