|
|
@ -353,11 +353,6 @@ Dispute Resolution Policy
|
|
|
|
Software suppliers who integrate the root certificates of CAcert
|
|
|
|
Software suppliers who integrate the root certificates of CAcert
|
|
|
|
into their software also assume a proxy role of Relying Parties,
|
|
|
|
into their software also assume a proxy role of Relying Parties,
|
|
|
|
and are subject to another licence.
|
|
|
|
and are subject to another licence.
|
|
|
|
<span class="q">
|
|
|
|
|
|
|
|
At the time of writing, the
|
|
|
|
|
|
|
|
"3rd Party Vendor - Disclaimer and Licence"
|
|
|
|
|
|
|
|
is being worked upon, but is neither approved nor offered.
|
|
|
|
|
|
|
|
</span>
|
|
|
|
|
|
|
|
</p>
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
<p>
|
|
|
@ -610,7 +605,7 @@ and messy process in order to get manufactured certificates.
|
|
|
|
</p>
|
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
<p>
|
|
|
|
<b>Psuedonymous Certificates.</b>
|
|
|
|
<b>Pseudonymous Certificates.</b>
|
|
|
|
Note that CAcert does not currently issue pseudonymous certificates,
|
|
|
|
Note that CAcert does not currently issue pseudonymous certificates,
|
|
|
|
being those with a name chosen by the Member and not verifiable
|
|
|
|
being those with a name chosen by the Member and not verifiable
|
|
|
|
according to documents.
|
|
|
|
according to documents.
|
|
|
@ -625,7 +620,7 @@ certificates.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
<p>
|
|
|
|
<b> Roots.</b>
|
|
|
|
<b>Roots.</b>
|
|
|
|
The <span class="q"> (new) </span> CAcert root layout is as below.
|
|
|
|
The <span class="q"> (new) </span> CAcert root layout is as below.
|
|
|
|
These roots are pending Audit,
|
|
|
|
These roots are pending Audit,
|
|
|
|
and will be submitted to vendors via the (Top-level) Root.
|
|
|
|
and will be submitted to vendors via the (Top-level) Root.
|
|
|
|