@ -21,6 +21,7 @@ H3 { color: #000000 }
TH P { color: #000000 }
-->
< / style > < / head >
< body style = "direction: ltr; color: rgb(0, 0, 0);" lang = "en-GB" >
< h1 > Assurance Policy for CAcert Community Members< / h1 >
< p > < a href = "PolicyOnPolicy.html" > < img src = "Images/cacert-wip.png" name = "graphics1" alt = "CAcert Policy Status" align = "bottom" border = "0" height = "33" width = "90" > < / a >
@ -28,75 +29,89 @@ TH P { color: #000000 }
Editor: Teus Hagen< br >
Creation date: 2008-05-30< br >
Last change by: Iang< br >
Last change date: 2008-07-09 16:14 MET< br >
Status: WIP 2008-05-30< br >
Next status: DRAFT 12th July 2008 < / p >
< h2 > 0. Preamble< / h2 >
< p > Definitions of terms: < / p >
Last change date: 2008-07-14 18:00 MET< br >
Status: DRAFT 2008-07-12< br >
Next status: POLICY 2008-09-30 < / p >
< h2 > < a name = "0" > 0.< / a > Preamble< / h2 >
< h3 > < a name = "0.1" > 0.1.< / a > Definition of Terms< / h3 >
< dl >
< dt > < i > Member< / i > < / dt >
< dd > A Member is an individual who has agreed to the CAcert
Community Agreement (< a href = "http://www.cacert.org/policy/CAcertCommunityAgreement.php" target = "_blank" > CCA< / a > ) and has created successfully
Community Agreement
(< a href = "http://www.cacert.org/policy/CAcertCommunityAgreement.php" target = "_blank" > CCA< / a > )
and has created successfully
a CAcert login account on the CAcert web site. < / dd >
< dt > < i > Assurance< / i > < / dt >
< dd > Assurance is the process by which a Member of CAcert
Community (Assurer) identifies an individual (< span lang = "en-US" > Assuree< / span > ).
< / dd >
< dt > < i > Prospective Member< / i > < / dt >
< dd > An individual who has been assured in an Assurance
process, but has not yet created successfully a CAcert login account. < / dd >
< dd > An individual who participates in the process of Assurance,
but has not yet created < s > < / s > < / dd >
< dt > < i > Name< / i > < / dt >
< dd > A Name is the full name of an individual, with all
< dd > A Name is the full name of an individual.
< s > < br > with all
components of that name.< / dd >
< dd >
(Title(s), first name(s), family name(s), name extensions,
abbreviation of name(s), etc. < br >
The Name is technically spoken a string exactly taken e.g. from a
governmental issued photo ID.) < / dd >
governmental issued photo ID.) < / s >
< / dd >
< dt > < i > Secondary Distinguishing Feature< / i >
(DoB) < / dt >
< dd > A Name for an individual is discriminated from similar
< / dt >
< dd > < b > An additional personal data item of the Member
that assists discrimination from Members with similar full names.
Currently this is the Date of Birth (DoB). < / b >
< s > A Name for an individual is discriminated from similar
full names by a secondary distinguished feature, as recorded on the
on-line CAcert (web) account. < br >
(Currently this is the date of birth (DoB) of the individual. )< / dd >
(Currently this is the date of birth (DoB) of the individual. )< / s >
< / dd >
< / dl >
< h3 >
The CAcert Web of Trust< / h3 >
< p > At each Assurance one allocates a number of Assurance Points,
applied to the assured Member. By combining the Assurances, and the
Assurance Points, CAcert constructs a global < i > Web-of-Trust< / i >
or
"WoT". < / p >
< h3 > < a name = "0.2" > 0.2.< / a > The CAcert Web of Trust< / h3 >
< p > < b > In face-to-face meetings,
an Assurer allocates a number of Assurance Points
to the Member being Assured.
CAcert combines the Assurance Points
into a global < i > Web-of-Trust< / i > (or "WoT").< / b >
< s > < br > At each Assurance one allocates a number of Assurance Points,
-applied to the assured Member. By combining the Assurances, and the
-Assurance Points, CAcert constructs a global < i > Web-of-Trust< / i > < / s > < / p >
< p > CAcert explicitly chooses to meet its various goals by
construction of a Web-of-Trust of all Members. This is done by
face-to-face meetings, identifying and sharing claims in a network.
Maintaining a sufficient strength for the Web-of-Trust is a
construction of a Web-of-Trust of all Members.
< s > This is done by
-face-to-face meetings, identifying and sharing claims in a network.< / s >
Maintaining a sufficient strength of the Web-of-Trust is a
high-level objective of the Assurance process. < / p >
< h3 > Related Documentation< / h3 >
< h3 > < a name = "0.3" > 0.3.< / a > < / h3 >
< p > Documentation on Assurance is split between this Assurance
Policy
(AP) and the < a href = "http://wiki.cacert.org/wiki/AssuranceHandbook2" target = "_blank" > Assurance
Handbook< / a > . The policy is controlled by Configuration Control
Specification (< a href = "http://wiki.cacert.org/wiki/PolicyDrafts/ConfigurationControlSpecification" target = "_blank" > CCS< / a > )
under Policy on Policy (< a href = "http://www.cacert.org/policy/PolicyOnPolicy.php" target = "_blank" > PoP< / a > )
policy document regime.< br >
Because Assurance is an active area, much
policy document regime. Because Assurance is an active area, much
of the practice is handed over to the Assurance Handbook, which is
not a controlled policy document, and can more easily respond to
experience and circumstances. It is also more readable. < / p >
< p > See also Organisation Assurance Policy (< a href = "http://www.cacert.org/policy/OrganisationAssurancePolicy.php" target = "_blank" > OAP< / a > )
and CAcert Policy Statement (< a href = "http://svn.cacert.org/CAcert/policy.htm" target = "_blank" > CPS< / a > ).
< / p >
< h2 > 1. Assurance Purpose< / h2 >
< h2 > < a name = "1" > < / a > < / h2 >
< p > The purpose of Assurance is to add confidence
in the Assurance Statement made by the CAcert Community of a Member. < / p >
< p > With sufficient assurances, a Member may: (a) issue
certificates
< p > With sufficient assurances, a Member may: (a) issue certificates
with their assured Name included, (b) participate in assuring others,
and (c) other related activities. The strength of these activities is
based on the strength of the assurance. < / p >
< h3 > The Assurance Statement< / h3 >
< p > The following claims can be made about a person who is
assured: < / p >
< h3 > < a name = "1.1" > 1.1.< / a > The Assurance Statement< / h3 >
< p > < b > The Assurance Statement makes the following claims
about a person< / b > :
< s > < br > The following claims can be made about a person who is
assured:< / s >
< / p >
< ol >
< li >
< p > The person is a bona fide Member. In other words, the
@ -113,68 +128,85 @@ issued by the Account; </p>
< / li >
< li >
< p > The Member is bound into CAcert's Arbitration as defined
by the Community Agreement; < / p >
by the CAcert C ommunity Agreement; < / p >
< / li >
< li >
< p > Some personal details of the Member are known to CAcert:
the individual Name(s), primary and other listed individual email
address(es), secondary distinguished feature (e.g. DoB). < / p >
address(es), secondary distinguish< b > ing< / b > < s > < / s > < / p >
< / li >
< / ol >
< p > The confidence level of the Assurance Statement is expressed
by
< p > The confidence level of the Assurance Statement is expressed by
the Assurance Points. < / p >
< h3 > Relying Party Statement< / h3 >
< h3 > < a name = "1.2" > 1.2.< / a > < / h3 >
< p > The primary goal of the Assurance Statement is for the express
purpose of certificates to meet the needs of the < i > Relying
Party
Statement< / i > , which latter is found in the Certification
Practice
purpose of certificates to meet the needs of the < i > Relying Party
Statement< / i > , which latter is found in the Certification Practice
Statement (< a href = "http://svn.cacert.org/CAcert/policy.htm" target = "_blank" > CPS< / a > ).
< / p >
< p > When a certificate is issued, some of the Assurance Statement
may
< p > When a certificate is issued, some of the Assurance Statement may
be incorporated, e.g. Name. Other parts may be implied, e.g.
Membership, exact account and status. They all are part of the
< i > Relying Party Statement< / i > . In short, this means that
other
< i > Relying Party Statement< / i > . In short, this means that other
Members of the Community may rely on the information verified by
Assurance and found in the certificate. < / p >
< p > In particular, certificates are sometimes considered to
provide
Assurance and found in the certificate.< / p >
< p > In particular, certificates are sometimes considered to provide
reliable indications of e.g. the Member's Name and email address. The
nature of Assurance, the number of Assurance Points, and other
policies and processes should be understood as limitations on any
reliance. < / p >
< h2 > 2. The Member< / h2 >
< h3 > 2.1 The Name in the CAcert login account< / h3 >
< p lang = "en-AU" > At least one individual Name is recorded
in the
CAcert login account. The Name is recorded as a string of characters,
encoded in < span lang = "en-US" > unicode< / span >
transformation format.< / p >
< p lang = "en-AU" > A Name should be as fully written in a
< h2 > < a name = "2" > 2.< / a > The Member< / h2 >
< h3 > < a name = "2.1" > 2.1.< / a > The < b > Member's< / b > Name < s > in the CAcert login account< / s > < / h3 >
< p > At least one individual Name is recorded in the Member's
CAcert login account. < b > The general standard of a Name is:< / b >
< / p >
< ul >
< li >
< p > The Name should be < b > recorded< / b > as < s > fully< / s > written in a
government-issued < b > photo< / b > identity document (ID).< / p >
< / li >
< p > < b > The Name should be recorded as completely as possible.
That is, including all middle names, any titles and extensions,
without abbreviations, and without transliteration of characters.
< / b >
< s > < br >
A Name should be as fully written in a
government-issued identity document (ID). A Name should be as
complete as possible, that is not abbreviated, no transliteration of
characters in the Name.< / p >
< p lang = "en-AU" > A Name in the CAcert login account, which
has reached
the applicable level of 50 Assurance Point is defined as an Assured
Name. An Assured Name can be used in a certificate issued by CAcert.
A Member with at least one Assured Name has reached the Assured
Member status.< / p >
< h3 > 2.2. Multiple Names and variations< / h3 >
< p > A Member may have multiple Names or multiple variations of a
characters in the Name.
< / s > < / p >
< / li >
< li >
< p > The Name is recorded as a string of characters,
encoded in < span lang = "en-US" > unicode< / span >
transformation format.< / p >
< / li >
< / ul >
< h3 > < a name = "2.2" > 2.2.< / a > Multiple Names and variations< / h3 >
< p >
< b >
In order to handle the contradictions in the above general standard,
a Member may record multiple Names or multiple variations of a Name
in her CAcert online Account.
Examples of variations include married names,
variations of initials of first or middle names,
abbreviations of a first name,
different language or country variations,
and transliterations of characters in a name.< / p >
< / b >
< s > < p >
A Member may have multiple Names or multiple variations of a
Name.
For example, married name, variations of initials of first or middle
names, abbreviation of a first name, different language or country
variations and transliterations of characters in a name.< / p >
< p > The login account may record multiple Names. Each of the
Assured
Names can be selected to be used in a certificate issued by CAcert.< / p >
< p > The login account may record multiple Names. Each of the Assured
Names can be selected to be used in a certificate issued by CAcert.
< / p > < / s >
<!--
FOLLOWING GOES TO ASSURER HANDBOOK
< h3 > Comparison of names< / h3 >
< h3 > < a name = "" > < / a > < / h3 >
< p > < a href = "http://en.wikipedia.org/wiki/Transliteration" target = "_blank" > Transliteration< / a >
of characters as defined in the transliteration character table (< a href = "http://svn.cacert.org/CAcert/Policies/transtab.utf" target = "_blank" > UTF
Transtab< / a > ) for names is permitted, but the result must be
@ -202,7 +234,7 @@ to have only a Name in the account which has no abbreviation(s), no
transliteration and is case sensitive.< / p >
FOLLOWING GOES TO Certficate Implementation Policy
< h3 > Names on the certificate issued by CAcert< / h3 >
< h3 > < a name = "" > < / a > < / h3 >
< p > The Certificate Implementation Policy (< a href = "http://svn.cacert.org/CAcert/Policies/CertificateImplementationPolicy.html" target = "_blank" > CIP< / a > )
will define the fields added by CAcert on the issued certificate on
request of the Member.< / p >
@ -311,9 +343,23 @@ is not checked by CAcert.</p>
Examples of names in
different contexts< / font > < / p >
-->
< h3 > 2.3. Status and Capabilities< / h3 >
< p > A Member has the following capabilities derived from
Assurance: < / p >
< h3 > < a name = "2.3" > 2.3.< / a > Status and Capabilities< / h3 >
< b >
< p > A Name which has reached
the level of 50 Assurance Points is defined as an Assured
Name. An Assured Name can be used in a certificate issued by CAcert.
A Member with at least one Assured Name has reached the Assured
Member status.
Additional capabilities are described in Table 1.< / p >
< / b >
< s > < p >
A Member has the following capabilities derived from
Assurance: < / p > < / s >
< blockquote >
< p align = "left" > < font size = "2" > < i > Table 1:
Assurance Capability< / i > < / font > < / p >
< table border = "1" cellpadding = "5" cellspacing = "0" >
< tbody >
< tr >
@ -351,7 +397,7 @@ allocation of Assurance Points is awaiting login account creation.</p>
< p align = "center" > 0< / p >
< / td >
< td >
< p align = "left" > r equest unnamed certificates< / p >
< p align = "left" > R equest unnamed certificates< / p >
< / td >
< td >
< p align = "left" > Member< / p >
@ -366,7 +412,7 @@ recorded in the account, they are not highly assured.</p>
< p align = "center" > 50< / p >
< / td >
< td >
< p align = "left" > r equest named certificates< / p >
< p align = "left" > R equest named certificates< / p >
< / td >
< td >
< p align = "left" > Assured Member< / p >
@ -381,7 +427,7 @@ assured to 50 Assurance Points or more</p>
< p align = "center" > 100< / p >
< / td >
< td >
< p align = "left" > b ecome an Assurer< / p >
< p align = "left" > B ecome an Assurer< / p >
< / td >
< td >
< p align = "left" > Prospective Assurer< / p >
@ -393,15 +439,20 @@ more) on at least one Name, and passing the Assurer Challenge.</p>
< / tr >
< / tbody >
< / table >
< p align = "center" > < font size = "2" > < i > table
Assurance Capability< / i > < / font > < / p >
< / blockquote >
< p > A Member may check the status of another Member, especially
for an
assurance process.< / p >
< p > The CAcert Policy Statement (< a href = "http://svn.cacert.org/CAcert/policy.htm" target = "_blank" > CPS< / a > )
for an assurance process.
< b >
Status may be implied from information in a certificate.
The number of Assurance Points for each Member is not published.
< / b >
< / p >
< p > The CAcert Policy Statement
(< a href = "http://svn.cacert.org/CAcert/policy.htm" target = "_blank" > CPS< / a > )
and other policies may list other capabilities that rely on Assurance
Points. < / p >
< h2 > 3. The Assurer< / h2 >
< h2 > < a name = "3" > 3.< / a > The Assurer< / h2 >
< p > An Assurer is a Member with the following: < / p >
< ul >
< li >
@ -413,7 +464,7 @@ Points. </p>
< / ul >
< p > The Assurer Challenge is administered by the Education Team on
behalf of the Assurance Officer. < / p >
< h3 > The Obligations of the Assurer< / h3 >
< h3 > < a name = "3.1" > 3.1.< / a > < / h3 >
< p > The Assurer is obliged to: < / p >
< ul >
< li >
@ -443,8 +494,8 @@ directed by the Arbitrator; </p>
Community. < / p >
< / li >
< / ul >
< h2 > 4. The Assurance< / h2 >
< h3 > 4.1. The Assurance Process< / h3 >
< h2 > < a name = "4" > < / a > < / h2 >
< h3 > < a name = "4.1" > < / a > < / h3 >
< p > The Assurer conducts the process of Assurance with each
Member. < / p >
< p > The process consists of: < / p >
@ -474,11 +525,11 @@ Distinguishing Feature, e.g., DoB); </p>
Assuree (Mutual Assurance); < / p >
< / li >
< li >
< p > Safe keeping of the CAcert Assurance Programme (< a href = "http://www.cacert.org/cap.php" target = "_blank" > CAP< / a > )
< p > Safekeeping of the CAcert Assurance Programme (< a href = "http://www.cacert.org/cap.php" target = "_blank" > CAP< / a > )
forms by Assurer. < / p >
< / li >
< / ol >
< h3 > 4.2. Mutual Assurance< / h3 >
< h3 > < a name = "4.2" > < / a > < / h3 >
< p > Mutual Assurance follows the principle of reciprocity. This
means
that the Assurance may be two-way, and that each member participating
@ -491,13 +542,17 @@ procedure and process, and is responsible for the results. </p>
the
Assurer, and reduces any sense of power. It is also an important aid
to the assurance training for future Assurers. < / p >
< s >
< h3 > 4.3. Evidence of Assurer status< / h3 >
< p > On the question of providing evidence that one is an Assurer,
CAcert Policy Statement (< a href = "http://svn.cacert.org/CAcert/policy.htm#p3.2" target = "_blank" > CPS< / a > )
says:< i > "The level at which each Member is Assured is public
data. The number of Assurance Points for each Member is not
published.< / i > .".< / p >
< h3 > 4.4. Assurance Points< / h3 >
< / s >
< h3 > < a name = "4.3" > 4.3.< / a > Assurance Points< / h3 >
< p > The Assurance applies Assurance Points to each Member which
measure the increase of confidence in the Statement (above).
Assurance Points should not be interpreted for any other purpose.
@ -525,45 +580,50 @@ information presented: </p>
< p > The Assurance Statement is confirmed. < / p >
< / li >
< / ul >
< p > Any lesser confidence should result in less Assurance Points
for a
< p > Any lesser confidence should result in less Assurance Points for a
Name. If the Assurer has no confidence in the information presented,
then < i > zero < / i > Assurance Points may be allocated by
the Assurer.
then < i > zero< / i > Assurance Points may be allocated by the Assurer.
For example, this may happen if the identity documents are totally
unfamiliar to the Assurer. The number of Assurance Points from < i > zero< / i >
to < i > maximum < / i > is guided by the Assurance Handbook
and the
judgement of the Assurer. < / p >
< p > Multiple Names should be allocated separately in a single
Assurance. < / p >
< p > A (new) Member who is not an Assurer may award an Assurer in a
reciprocal process a maximum of 2 Assurance Points, according to his
and the judgement of the Assurer.
< b >
If there is negative confidence the Assurer should consider
filing a dispute.< / b > < / p >
< p > Multiple Names should be allocated Assurance Points
independently within a single Assurance. < / p >
< p > A < s > (new)< / s > Member who is not an Assurer may award an Assurer in a
reciprocal process a maximum of 2 Assurance Points, according to
< b > her< / b > < s > his< / s >
judgement. The Assurer should strive to have the Member allocate
according to the Member's judgement, and stay on the cautious side a
maximum of Assurance Points per Name; a (new) Member new to the
assurance process should allocate < i > zero< / i > Assurance
Points
until they get some confidence in what is happening.< / p >
< p > To reach 50 Assurance Points for a Name the Member must
according to the Member's judgement, and stay on the cautious side
< s > a maximum of AssurancePoints per Name< / s > ;
the < s > (new)< / s > Member new to the assurance process
should allocate < i > zero< / i > Assurance Points
until < b > she gains< / b > < s > they gets< / s > some confidence in what is happening.< / p >
< p > < b > In general, for a Member to reach 50 Assurance Points, the Member must
have participated in at least two assurances, and
at least one Name will have been assured to that level.< / b >
< s > < br > To reach 50 Assurance Points for a Name the Member must
have had at least two assurances on that Name: the Assured Member has
at least one Name assured, the Assured Name.< / p >
at least one Name assured, the Assured Name.< / s >
< / p >
< p > To reach 100 Assurance
Points, at least one Name of the Assured Member must have been
assured at least three times.< / p >
< p > The maximum number of
Assurance
Points, which can be allocated for a Name assurance under this policy
and subsidiary policies is 50 Assurance Points.< / p >
< p > If there is negative confidence the Assurer should consider
filing
a dispute.< / p >
< h3 > 4.5. Experience Points< / h3 >
< p > The maximum number of Assurance
Points which can be allocated for an < s > Name< / s > Assurance under this policy
and < b > under any act under any< / b >
Subsidiary Policy (below) is 50 Assurance Points.< / p >
< h3 > < a name = "4.4" > 4.4.< / a > Experience Points< / h3 >
< p > The maximum number of Assurance Points that may be awarded by
an
Assurer is determined by the Experience Points of the Assurer. < / p >
< dl >
< dd >
< blockquote >
< p align = "left" > < font size = "2" > < i > Table 2:
Maximum of Assurance Points < / i > < / font >
< / p >
< table border = "1" cellpadding = "2" cellspacing = "0" width = "15%" >
< tbody >
< tr >
@ -624,11 +684,7 @@ Assurer is determined by the Experience Points of the Assurer. </p>
< / tr >
< / tbody >
< / table >
< / dd >
< / dl >
< p align = "left" > < font size = "2" > < i > table
Maximum of Assurance Points < / i > < / font >
< / p >
< / blockquote >
< p > An Assurer is given a maximum of 2 Experience Points for every
completed Assurance. On reaching Assurer status, the Experience
Points start at 0 (zero). < / p >
@ -640,7 +696,7 @@ permanently to an Assurer by CAcert Inc.'s Committee (board), on
recommendation from the Assurance Officer. < / p >
< p > Experience Points are not to be confused with Assurance
Points. < / p >
< h3 > 4.6. CAcert Assurance Programme (CAP) form< / h3 >
< h3 > < a name = "4.5" > 4.5.< / a > < / h3 >
< p > The CAcert Assurance Programme (< a href = "http://www.cacert.org/cap.php" target = "_blank" > CAP< / a > )
form requests the following details of each Member or Prospective
Member: < / p >
@ -692,7 +748,7 @@ required as well; </p>
< / ul >
< p > The CAP forms are to be kept at least for 7 years by the
Assurer. < / p >
< h2 > 5. The Assurance Officer< / h2 >
< h2 > < a name = "5" > < / a > < / h2 >
< p > The Committee (board) of CAcert Inc. appoints an Assurance
Officer
with the following responsibilities: < / p >
@ -732,57 +788,50 @@ procedures or guidelines; </p>
(web-of-trust) to meet the agreed needs of the Community. < / p >
< / li >
< / ul >
< h2 > 6. Subsidiary Policies< / h2 >
< p > The Assurance Officer manages various exceptions and
additional
< h2 > < a name = "6" > 6.< / a > Subsidiary Policies< / h2 >
< p > The Assurance Officer manages various exceptions and additional
processes. Each must be covered by an approved Subsidiary Policy
(refer to Policy on Policy => CAcert Official Document COD1).
Subsidiary Policies specify any additional tests of knowledge
required and variations to process and documentation, within the
general standard stated here. < / p >
< h3 > 6.1. Standard< / h3 >
< h3 > < a name = "6.1" > < / a > < / h3 >
< p > Each Subsidiary Policy must augment and improve the general
standards in this Assurance Policy. It is the responsibility of each
Subsidiary Policy to describe how it maintains and improves the
specific and overall goals. It must describe exceptions and potential
areas of risk. < / p >
< h3 > 6.2. High Risk Applications< / h3 >
< h3 > < a name = "6.2" > < / a > < / h3 >
< p > In addition to the Assurance or Experience Points ratings set
here
in and in other policies, Assurance Officer or policies can
here and in other subsidiary policies, the Assurance Officer or policies can
designate certain applications as high risk. If so, additional
measures may be added to the Assurance process that specifically
address the risks.< / p >
< p > Additional measures may include additional information.
Additional
information can be required in process of assurance: < / p >
< p > Additional measures may include < s > additional information< / s > :
< ul >
< li > < dd > unique numbers of identity documents; < / dd >
< / li >
< li > < dd > photocopy of identity documents; < / dd >
< / li >
< li > < dd > photo of User; < / dd >
< / li >
< li > < dd > address of User. < / dd >
< / li >
< li >
Additional information can be required in process of assurance: < / p >
< ul >
< li > unique numbers of identity documents,< / li >
< li > photocopy of identity documents,< / li >
< li > photo of User,< / li >
< li > address of User.< / li >
< / ul >
< p > Additional Information is to be kept by Assurer, attached to
CAcert Assurance Programme (< a href = "http://www.cacert.org/cap.php" target = "_blank" > CAP< / a > )
form. Assurance Points allocation by this assurance is unchanged.
User's CAcert login account should be annotated to record type of
additional information: < / p >
< ul >
additional information; < / p >
< / li >
< li >
< p > Arbitration: < / p >
< ul >
< li >
< p > Member to participate in Arbitration. This confirms
< li > Member to participate in Arbitration. This confirms
their acceptance of the forum as well as trains in the process and
import < / p >
import,
< / li >
< li >
< p > Member to file Arbitration to present case. This
allows Arbitrator as final authority; < / p >
< li > Member to file Arbitration to present case. This
allows Arbitrator as final authority;
< / li >
< / ul >
< / li >
@ -803,7 +852,7 @@ support administrators. </p>
< / ul >
< p > Applications that might attract additional measures include
code-signing certificates and administration roles. < / p >
< h2 > 7. Privacy< / h2 >
< h2 > < a name = "7" > < / a > < / h2 >
< p > CAcert is a "privacy" organisation, and takes the
privacy of its Members seriously. The process maintains the security
and privacy of both parties. < / p >
@ -829,6 +878,6 @@ administration when operating under the authority of Arbitrator or
under CAcert policy. < / p >
< / li >
< / ul >
< p > < a href = "http://validator.w3.org/check?uri=referer" > < img src = " ../ Images/valid-xhtml11-blue" name = "graphics2" alt = "Valid XHTML 1.1" align = "bottom" border = "0" height = "33" width = "90" > < / a >
< p > < a href = "http://validator.w3.org/check?uri=referer" > < img src = " Images/valid-xhtml11-blue" name = "graphics2" alt = "Valid XHTML 1.1" align = "bottom" border = "0" height = "33" width = "90" > < / a >
< / p >
< / body > < / html >
Ian Grigg
16 years ago