CAcert Code Development list.

[dirk astrath <dastrath AT gmx.de>]

hiya,

while implementing the patches for the storage of the CCA-agreement,
some questions came up ...

(a)     database-structure:

a short discussion between ian, philipp and me showed, that a new table
should be used to store the data ... so i did:

CREATE TABLE  `cacert`.`users_agreements` (
  `ID` int(11) NOT NULL auto_increment,
  `users_id` int(11) NOT NULL,
  `secondary_users_id` int(11) default NULL,
  `document` varchar(50) default NULL,
  `date` datetime default NULL,
  `type` varchar(10) NOT NULL,
  `comment` varchar(100) NOT NULL,
  `usercomment` varchar(100) default NULL,
  PRIMARY KEY  (`ID`)
) ENGINE=MyISAM AUTO_INCREMENT=8 DEFAULT CHARSET=utf8

Let me explain this structure:

Normally the fields are used in the following way:
users_id        from users-table
document        'CCA' as a fixed string up to now
date            date of agreement (=now)
type            'Active' as a fixed string
comment         using 'which' action (Join, ...)
... other fields stay NULL ...

at an assurance this behavior changes a little bit:
users_id        from users-table
document        'CCA' as a fixed string up to now
date            date of agreement (=now)
type            'Active' or 'Passive' as a fixed string
comment         using 'which' action (Assured by/Assuring)
secondary_users_id      The 'opposite part at an assurance

... which means: during an assurance two records are created ... one for
the assurer (active) and one for the applicant (passive)

the field 'usercomment' stays empty at the moment ... it may be used
later when the user has to sign/... the agreement

However: Most of this work is done ... if there are no request-changes,
i'll put the patches on test1.cacert.at before weekend (hopefully ...
;-) ) so everything can be tested ...

Now it's your part to send the wishes for these patches ... ;-)

have a nice day ...

ps: as far as i heard from ian, it's really necessary for the audit to
ask for CCA before generating certificates, signing pgp-keys etc. ...

Attachment: signature.asc
Description: OpenPGP digital signature