CAcert Code Development list.

[Bernhard Froehlich <ted AT convey.de>]

dirk astrath schrieb:
> hiya ian,
>
> > > (e.g. without acceptance of CCA you will not be able to generate
> > > certificates/assure/...
> > right.  It sounds like a good feature, I'm just not sure where it 
> > would be used;  where would we record that the member DID NOT agree?  
> > It will come up one day, I'm sure.  But we can probably leave it 
> > until then?
>
> however ... it's no problem to add an additional field in the database 
> now ... unsure, if it's used later ... ;-)

My idea was to differentiate between users which did login till now and 
those who did try to login but dod not accept the CCA. And maybe we 
still want to allow those ... dissenters to do some non-critical things 
(like using the support web form).
> [...]
> > The Assurer can be relied upon to correctly click on the "applicant 
> > accepted CCA" box when completing the assurance.  It's his job!  And 
> > he has the evidence of the CCA form, and this will reinforce the need 
> > for him to do it.
>
> correct ... but most other things at cacert rely on a minimum of three 
> assurers.

So the checkbox should be shown and a record is created on every 
Assurance. Then we'll have enough redundancy!

> [...]
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