Sophie: xca-0.7.0-1mdv2010.0 i586

xca-0.7.0-1mdv2010.0.i586.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
 <TITLE>XCA : Certificate Signing Requests </TITLE>
 <LINK HREF="xca-9.html" REL=next>
 <LINK HREF="xca-7.html" REL=previous>
 <LINK HREF="xca.html#toc8" REL=contents>
</HEAD>
<BODY>
<A HREF="xca-9.html">Next</A>
<A HREF="xca-7.html">Previous</A>
<A HREF="xca.html#toc8">Contents</A>
<HR>
<H2><A NAME="csr"></A> <A NAME="s8">8.</A> <A HREF="xca.html#toc8">Certificate Signing Requests </A></H2>

<P>Certificate signing requests are described in PKCS#10 standard.
They are used to supply a Certification Authority with the 
needed information to issue a valid certificate for you,
without knowing your private key. This
includes your personal information, your public key and additional extensions.</P>
<P>Netscape SPKAC files can not be created or exported, but they can be imported and signed.
This requests are marked in the Signature field as SPKAC and a Netscape icon is
shown.</P>

<H2><A NAME="ss8.1">8.1</A> <A HREF="xca.html#toc8.1">Generating a new Request</A>
</H2>

<P>After clicking on the <CODE>New Request</CODE> button the Certificate dialog will be started to ask
all needed information for generating a new Request. See: 
<A HREF="xca-6.html#wizard">The Certificate input dialog</A></P>
<P>The request generation can also be invoked by the context menu of a certificate (Export->Request).
This menu point is only available if the private key of the certificate is available.
In this case all needed data is copied from the certificate and the Wizard is not invoked.</P>

<H2><A NAME="ss8.2">8.2</A> <A HREF="xca.html#toc8.2">Request export</A>
</H2>

<P>Requests can be exported by the context-menu or by the button on the right.
The filename and type can be selected in the next dialog.</P>

<H2><A NAME="ss8.3">8.3</A> <A HREF="xca.html#toc8.3">Request details</A>
</H2>

<P>All information contained in the request are shown. If the keystore contains
the private key corresponding to the request the keys internal name is shown
in the <CODE>Key</CODE> field.</P>


<HR>
<A HREF="xca-9.html">Next</A>
<A HREF="xca-7.html">Previous</A>
<A HREF="xca.html#toc8">Contents</A>
</BODY>
</HTML>