CPS Technical Solutions #2

CPS Technical Solutions

0. Introduction, concepts

1. Types of certificates: PGP, X.509, client, server, root CA, intermediate CA.

2. Purposes of a user certificate - what it is used for - templates, restrictions, legal conotations

3. User certificate requirements given by the rules from above (CAB)

a) validity max. 1 year

b) user certs should be signed only by the intermediate CA certificate

4. CAcert User Certificate Issuance Rules (Client and Server)

a) up to 49 APs

b) 50-99 APs

c) 100+ APs

d) assurer - ability to sign documents, software

5. Certificate templates

a) client

b) server

c) PGP ?

6. Certificate structure

a) X.509: data, from where (CSR, user account, template)

b) dtto for PGP

7. Other (critically according to existing CPS)

# CPS Technical Solutions ## 0. Introduction, concepts ## 1. Types of certificates: PGP, X.509, client, server, root CA, intermediate CA. ## 2. Purposes of a user certificate - what it is used for - templates, restrictions, legal conotations ## 3. User certificate requirements given by the rules from above (CAB) ### a) validity max. 1 year ### b) user certs should be signed only by the intermediate CA certificate ## 4. CAcert User Certificate Issuance Rules (Client and Server) ### a) up to 49 APs ### b) 50-99 APs ### c) 100+ APs ### d) assurer - ability to sign documents, software ## 5. Certificate templates ### a) client ### b) server ### c) PGP ? ## 6. Certificate structure ### a) X.509: data, from where (CSR, user account, template) ### b) dtto for PGP ## 7. Other (critically according to existing CPS)

Hi @alkas,

pull requests are meant to discuss changes to existing files or new files in a repository. From a git perspective this pull request is empty because it contains no git commits.

The normal process to create a pull request is the following:

clone the repository to your machine

git clone https://code.cacert.org/cacert/cacert-policies.git

create a branch for your planned modifications
```
git checkout -b your-branch-name
```
edit or add files in your local clone of the repository

add and commit your changes

git commit -a -m "Structure for CPS Technical Solutions"

Push your changes to the central repository
```
git push -u origin your-branch-name
```

When you push your changes the git client will show advice how to create a pull request to merge the changes from your-branch-name to the main branch. This pull request can then be reviewed and discussed with other contributors. Modifications to the pull request itself can be added by committing/pushing additional changes to the your-branch-name branch.

You may also edit files in the browser, but this is quite limited in comparison to the workflow described above.

Kind regards
Jan

Hi @alkas, pull requests are meant to discuss changes to existing files or new files in a repository. From a git perspective this pull request is empty because it contains no git commits. The normal process to create a pull request is the following: 1. clone the repository to your machine ``` git clone https://code.cacert.org/cacert/cacert-policies.git ``` 2. create a branch for your planned modifications ``` git checkout -b your-branch-name ``` 3. edit or add files in your local clone of the repository 4. add and commit your changes ``` git commit -a -m "Structure for CPS Technical Solutions" ``` 5. Push your changes to the central repository ``` git push -u origin your-branch-name ``` When you push your changes the git client will show advice how to create a pull request to merge the changes from your-branch-name to the main branch. This pull request can then be reviewed and discussed with other contributors. Modifications to the pull request itself can be added by committing/pushing additional changes to the your-branch-name branch. You may also edit files in the browser, but this is quite limited in comparison to the workflow described above. Kind regards Jan

Thank you, @jandd !
I have reviewed and approved that PR, so it's now visible on the first page of the repo of the policies.
https://code.cacert.org/cacert/cacert-policies

@alkas if we use this method, described by Jan, then all text suggestions will be visible here in the repo, so we can discuss them, and not have to send emails back and forth.

Also, THANK YOU, @alkas ! for picking up the baton where I so clearly dropped it, and pushing forward with this process of improving the CPS.

Thank you, @jandd ! I have reviewed and approved that PR, so it's now visible on the first page of the repo of the policies. https://code.cacert.org/cacert/cacert-policies @alkas if we use this method, described by Jan, then all text suggestions will be visible here in the repo, so we can discuss them, and not have to send emails back and forth. Also, THANK YOU, @alkas ! for picking up the baton where I so clearly dropped it, and pushing forward with this process of improving the CPS.

Labels Milestones