• SystemAdministration

The System Administration team is responsible for operation and maintenance of the servers and services provided by CAcert.

Talking to us

• Contact your local sysadmin directly using the FULL LISTING or the system-admin@cacert.org aliases.

• For more general things, join the Sysadm Maillist and ask there.

• For more formal things (bug reports) mail to support@cacert.org.

People

Iang: possibly we want to break this page out into the the three applicable teams, and have some top-level indexes referring to the individual areas?

Infrastructure team

• Philipp Gühring - hashserver (??)

• Daniel Black - email, lists, community, blog

• Ted - CATS

• Mario Lipinski - wiki, issue

• Bas van den Dikkenberg - help with issue tracking (??)

• Markus Warg - webmail and translingo

• Stefan Freudenberg - blog

• Jan Dittberner - svn, cod and eventually development support tools

• Lance Davis - system logging / IDS (??)

• Christopher Hoth - email, lists, forum

Future(?)

• Kees van Eeten, Ben Pollinger - Forum
• Philippe Teuwen - OpenID

We are always looking for new System Administrators, and would be glad to hear from you. Please send a short introduction how you'd like to help to daniel@cacert.org or join the Sysadm Maillist and ask there.

Critical Servers team

• Mendel Mobach (BIT)

• Wytze van der Raay (BIT)

• Stefan Kooman (BIT)

• maybe starting May 2009 Marco Hermans

• transition Philipp

Above, people marked (BIT) above are listed on the Firewall/OS Access list in Appendix B, MoU with Oophaga. These people are able to get direct physical (console) access to the machines with Oophaga assistance under SecurityManual.

Access Engineers Team

• Bas van den Dikkenberg
• Hans Verbeek
• Rudi van Drunen
• Rudi Engelbertink

Access Engineers provide physical gate-keeping to the BIT facility. They have to be present for all direct access by Critical admins. They are listed on the (x?) Access list in Appendix B, MoU with Oophaga.

Documents

• The System Administrator's "bible" is the SecurityManual.

• which is ruled by the (DRAFT) Security Policy. As the SP is now in DRAFT, it is binding on the system administrators (more precisely the critical sysadm team and the access engineers team).

• All are under CCA as Members of CAcert. All are also Assurers, so are fully known to us. All are encouraged to be members of the Association so as to have a say in big community decisions.

• See also the (DRAFT) CPS which describes what it is the application delivers.

• Principles of CAcert and some common good practices regarding privacy and professionalism from SAGE's Code of Ethics.

List of Guides:

List of Procedures:

Projects:

• new Host for Infrastructure

Systems

List of Systems:

Roles

• Public Services
• Revocation Services
• Support for CATS, audit
• test services

• CategorySupport

• CategoryInfrastructure