diff --git a/TVerifyAssurancePolicy.html b/TVerifyAssurancePolicy.html index f31b47b..a484eb9 100644 --- a/TVerifyAssurancePolicy.html +++ b/TVerifyAssurancePolicy.html @@ -1,240 +1,207 @@ - - -Third Party Verification System Policy - - -

Third Party Verification System Policy

- -

Preamble

- -

-This is a subsidiary policy under Assurance Policy (COD13). -It documents the acceptance of Thawte-issued certificates -and disclosers as inputs into the assurance process. -

- -

Third Party Certificate

- - -

-The CAs listed in Appendix A are approved to "this system". -

- -

-If a certificate is examined by an Assurer (e.g., signed email) -and determined to provide evidence of a Name and email address that -matches the Name stored in the CAcert system, -the Assurer may allocate 25 (???) Assurance Points -(or as determined in the Appendix A). -

- -

-This is only available to Assurers who are: -

- -
  1. - Full Assurer with 50 Experience Points -
  2. - Assigned the Tverify role by support. -
- -

-This may be only awarded once per Member. -

- -

-This may be done automatically by the existing -Tverify system. -

- - -

Other Web of Trust

- -

-Webs of Trust listed in Appendix B are approved for this system. -

- -

-If evidence of full "assurer status" in the other Web of Trust -is provided to an Assurer, -then the Assurer may award 25 Assurance Points, -in addition to the above 25 points from the certificate. -

- -

-The Assurer must go to the other system and verify the -Name. -And DoB??? But the user has to enable each Assurer to -check the DoB by means of the permitting an assurance in the -other system. -

- -

-Assurers enabled for this system must be: -

- -
  1. - Full Assurer with 50 Experience Points -
  2. - Assigned the Tverify role by support. -
  3. - Full "assurer status" in the other system. -
- -

-This may be only awarded once per Member. -

- -

-What about voting system.... -

- - - - -
  • - - optional : - the user provides the web link in the directory of Thawte - notaries. The user must display his name and CAcert account email - address in the directory assurer message. The user can get 40 extra - points after manual checking, - - - -
  • - optional: - The user provides a scan of a government photo id. The user - can get an extra 60 points after manual checking. - -
  • - -

    - Agreed that experience as TN is not useful for CAcert Experience Points. -So Maximum is 100. -

    - -

    Manual Points Allocation

    - -

    - If the user completes only step 1, the users get 50 points if the - Thawte name matches the CAcert name : The process is fully automated and - the user still can do later the optional steps. -

    - -

    - In case the user completes steps 2 or 3, a Tverify-authorised Assurer does the following manual checks : -

    - - -
    1. - check if the link to the Thawte WoT directory matches the name and - email address of the CAcert account, and -
    2. - - check if the photo id macthes the name and date of birth of the CAcert - account. -
    - -

    -the CAcert Tverify community member votes Aye or Nay on the request -(faithfullness) and optionally adds a comment on the reason why they reject -the request. -

    - -

    -If the requests gets 4 Naye, the requests is rejected, the user has to -restart the process. -

    - -

    -if the request gets 4 Aye, the requests is completed and the appropriate -amount of Assurance points are added to the account, logged as an Tverify -assurance. -BY WHOM? -

    - -

    -Each user step can granted points only once. The maximum is 150 points. -BLECH -

    - -

    Manual Points Allocation

    - -

    -To be a Tverify Assurer, an Assurer must have: -

    - - - -

    -Authorisation is done by .... - the Support Officer (and confirmed by ??? Assurance Officer). -

    - -

    -Currently there are 7+ Assurers who are authorised to conduct the -Tverify additional procedure. -

    - -

    System

    - -

    -An online system is run to accept the certificate. -This is located at https://tverify.cacert.org/ -This is a critical / non-critical system ???? -

    - -

    Legal

    - -

    -WHat do the Thawte docs say about reliance, etc. -Is there a possibility to do this? -What is the liability position? -Chances are, there is no liability and no reliance permitted. -Which means ... there is no reliance on the Name in the cert. -

    - - - -

    OLD stuff

    -
    OLD: -

    - mandatory : the users provides a - Thawte assured certificate including the user name. - If the name and email address in the certificate matches - the name and email address recorded by CAcert exactly, - the user is given 50 Assurance Points automatically - by the online system. -

    - - -
    - + + + + + Third Party Verification System Policy + + + + + +

    Third Party Verification System Policy

    +

    Preamble +

    +

    This is a subsidiary policy under Assurance Policy (COD13). It +documents the acceptance of Thawte-issued certificates and disclosers +as inputs into the assurance process. +

    +

    Third Party Certificate +

    +

    The CAs listed in Appendix A are approved to "this system". +

    +

    If a certificate is examined by an Assurer (e.g., signed email) +and determined to provide evidence of a Name and email address that +matches the Name stored in the CAcert system, the Assurer may +allocate 25 (???) Assurance Points (or as determined in the Appendix +A). +

    +

    This is only available to Assurers who are: +

    +
      +
    1. Full Assurer with 50 Experience + Points +

      +
    2. Assigned the Tverify role by support. +

      +
    +

    This may be only awarded once per Member. +

    +

    This may be done automatically by the existing Tverify system. +

    +

    Other Web of Trust +

    +

    Webs of Trust listed in Appendix B are approved for this system. +

    +

    If evidence of full "assurer status" in the other Web of +Trust is provided to an Assurer, then the Assurer may award 25 +Assurance Points, in addition to the above 25 points from the +certificate. +

    +

    The Assurer must go to the other system and verify the Name. And +DoB??? But the user has to enable each Assurer to check the DoB by +means of the permitting an assurance in the other system. +

    +

    Assurers enabled for this system must be: +

    +
      +
    1. Full Assurer with 50 Experience + Points +

      +
    2. Assigned the Tverify role by + support. +

      +
    3. Full "assurer status" in the other system. +

      +
    +

    This may be only awarded once per Member. +

    +

    What about voting system.... +

    + + + + +

    Agreed that experience as TN is not useful for CAcert +Experience Points. So Maximum is 100. +

    +

    Manual Points Allocation +

    +

    If the user completes only step 1, the users get 50 points if the +Thawte name matches the CAcert name : The process is fully automated +and the user still can do later the optional steps. +

    +

    In case the user completes steps 2 or 3, a Tverify-authorised +Assurer does the following manual checks : +

    +
      +
    1. check if the link to the Thawte + WoT directory matches the name and email address of the CAcert + account, and +

      +
    2. check if the photo id macthes the name and date of birth of + the CAcert account. +

      +
    +

    the CAcert Tverify community member votes Aye or Nay on the +request (faithfullness) and optionally adds a comment on the reason +why they reject the request. +

    +

    If the requests gets 4 Naye, the requests is rejected, the user +has to restart the process. +

    +

    if the request gets 4 Aye, the requests is completed and the +appropriate amount of Assurance points are added to the account, +logged as an Tverify assurance. BY WHOM? +

    +

    Each user step can granted points only once. The maximum is 150 +points. BLECH +

    +

    Manual Points Allocation +

    +

    To be a Tverify Assurer, an Assurer must have: +

    + +

    Authorisation is done by .... the Support Officer (and confirmed +by ??? Assurance Officer). +

    +

    Currently there are 7+ Assurers who are authorised to conduct the +Tverify additional procedure. +

    +

    System +

    +

    An online system is run to accept the certificate. This is located +at https://tverify.cacert.org/ This is a critical / non-critical +system ???? +

    +

    Legal +

    +

    WHat do the Thawte docs say about reliance, etc. Is there a +possibility to do this? What is the liability position? Chances +are, there is no liability and no reliance permitted. Which means +... there is no reliance on the Name in the cert. +

    +

    OLD stuff +

    +
    OLD: +
    +
    mandatory : the users provides a Thawte assured +certificate including the user name. If the name and email address in +the certificate matches the name and email address recorded by CAcert +exactly, the user is given 50 Assurance Points automatically by the +online system. +
    + + + \ No newline at end of file