miti
/
linux-sgx-trts-modified


			
				
					
						
						
							12345678910111213141516171819202122232425262728293031323334353637
							<!--------------------------------------------------------------------------->
<!-- Copyright (c) 2016 Intel Corporation.				   -->
<!-- 									   -->
<!-- All rights reserved. This program and the accompanying materials	   -->
<!-- are made available under the terms of the Eclipse Public License v1.0 -->
<!-- which accompanies this distribution, and is available at		   -->
<!-- http://www.eclipse.org/legal/epl-v10.html				   -->
<!-- 									   -->
<!-- Contributors:							   -->
<!--     Intel Corporation - initial implementation and documentation	   -->
<!--------------------------------------------------------------------------->
<?xml version="1.0" encoding="utf-8"?>
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" MadCap:lastBlockDepth="4" MadCap:lastHeight="1043" MadCap:lastWidth="652">
    <head><title>Updating SGX Enclave Signing Key</title>
        <link href="Resources/Stylesheets/intel_css_styles.css" rel="stylesheet" type="text/css" />
    </head>
    <body>
        <h2>Updating SGX Enclave Signing Key</h2>
        <p>All skeletons enclave samples produced by the plugin contain a sample signing key.  You might want to import another sign key that you already have, or generate a new one.   Use the command <b>Update SGX Enclave Signing Key</b> to complete this task.</p>
        <ol>
            <li>Choose  <b>Update SGX Enclave Signing Key</b> by right-click on the project in <b>Project Explorer -&gt; Software Guard Extension Tools</b> menu. The <b>Import or (Re)Generate Enclave Signing Key</b> dialog appears.</li>
            <li>In the <b>Import or (Re)Generate Enclave Signing Key</b> dialog, click <b>Select</b> to open a file dialog to select the output key.</li>
            <li>
                <p>Click <b>Improt Key</b> to update a selected signing key by copying another existing key  or click <b>Generate Key</b> to update the selected signing key by generating a new key. In both cases, the new signature key is put into the file in text field <b>Enclave Signing Key</b>.</p>
                <p>
                    <img src="Resources/Images/Import_or_Re_Generate_Enclave_Signing_Key.png" />
                </p>
                <p class="figcap">Import or (Re)Generate Enclave Signing Key</p>
            </li>
            <li>Click <b>OK</b> to update the enclave signing key.</li>
        </ol>
        <p>Under the hood, a new key is generated using openssl*, which needs to be installed on the machine:</p>
        <p><code>openssl genrsa -out ../../../encl1_private.pem.key.pem -3 3072</code>
        </p>
        <p><![CDATA[	]]></p>
    </body>
</html>