Policy-Discussion

[Bernhard Froehlich <ted AT convey.de>]

Duane schrieb:
> Bernhard Froehlich wrote:
>
>   
> > > The 2 photo ID thing was only supposed to be for TTP, in person
> > > assurances only required 1 photo ID, for exactly the reasons you outline.
> > >   
> > >       
> > So this IS policy? One photo ID is enough for in person assurances? I
> > have seen many assurers (one of them quite occasionally in my bathroom
> > mirror) which insist that at least two photo IDs are required!
> > Probably the statements on those wiki pages are from me, so I'll have to
> > correct them (after having cross-checked the CPS once more).
> >     
>
> It's clearly written on the Assurance form that two govt issued IDs are
> required, one MUST be a photo ID, I thought that should have been
> official enough.
>   
Hey, great idea to read that!  ;)

The form I just downloaded from the server reads "... and verified their 
identity against one or more original, trusted, government photo 
identity documents." So I'd assume from this that even a single govt 
issued photo ID would suffice.

Now I had a look at the current CPS using 
http://www.cacert.org/cps.php#p5.2 (by the way, is there any other way 
beside asking Google to find this page?):
>>>>>>>>>>
To have trust points issued in a face to face meeting there is strict 
guidelines on how this must be achieved to be recognised by CAcert:

   * the person issuing the trust points must see 2 forms of photo ID:
     At least one photo ID must be issued by a government body.
     Acceptable forms of ID include Passports, Drivers Licenses and ID
     Cards

<<<<<<<<<<<
Which is rather close to the statement on the form as well as your 
statement, but not quite identical to either one...
Maybe the forms should be adjusted to the CPS, or is the CPS due to 
adapt to the form?

Ted
;)

--
PGP Public Key Information
Download complete Key from http://www.convey.de/ted/tedkey_convey.asc
Key fingerprint = 31B0 E029 BCF9 6605 DAC1  B2E1 0CC8 70F4 7AFB 8D26

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature