• Brain
• CAcertInc
• Committee
• MeetingAgendasAndMinutes
• 2025-03-06

• To Brain CAcert Inc. - CAcert.org Members Association - General Meetings - To Brain CAcert Inc. Committee Meeting Agendas & Minutes - Board's Project Overview - Current Action Items - last meeting - next meeting

Committee Meeting 2025-03-06 19:00 UTC

The meeting will take place at 19:00 UTC at https://meet.jit.si/cacert If you do not have audio channel, you may try in the IRC channel #board-meeting on the CAcert IRC network.

Agenda

Signs that appear in the agenda
Formulated motion on your topic. It will be put to the vote. Adjustments may be made before the vote. A motion must be submitted for resolutions!
Information for your attention. Does not need to be explained or discussed at the meeting. Purpose: Everyone is up to date. (max. 10 seconds)
Discussion topic with or with no decision.

1. Preliminaries
   1. Chair opens the Committee Meeting

   2. Who Secretary is making minutes ?

   3. Accept minutes from 30. Jan. 2025 "I move to accept the minutes of the committee meeting of 30. Jan 2025."

   4. Chair asks whether cacert-board-private or cacert-board maillist or Threema chat or Telegram group includes any items that need to be disclosed to Members.

   5. Agree on the 3rd of April 2025, 18:00 UTC as date for the next committee meeting. (Following dates probably, 8th of May, 5th of June 2025)

   6. Agree that the meetings after this (until october) will start at 18:00 UTC to remain 20:00 in Central Europe and 14:00 in New York during DST period.
2. Business

   1. OpenID Connect (Brian, Dirk, S.T.)

      1. Last steps: by ? (lead) and ? (help) until ?
      2. Documentation: by ? (lead) and ? (help) until ?

   2. CAcert Spain (Etienne)

      1. Draft; result of wednesday discussion (Brian, Dirk, Kim)
      2. Next steps

   3. OrgA (Alex, Etienne)

      1. reactivaction, admin rigths

      2. physical meeting in week 25.-29. March 2025

   4. Support Support

      1. OpenID @wiki & @blog (who shares infos with secretary?)

      2. Let's Encrypt @wiki & @blog (Dirk's report repushed for March)

      3. Progress report: To delete accounts of users who are org-admins, any rule, arbitrator act, or a technical intervention is needed. --> confirmation that Firewall2 is updated and instructions given to Aleš by Dirk.

      4. CPS Introduction for PolG is missing --> task of the secretary

   5. CAcert Youth Projects (2.5 in December 2024) -- no information this month.

   6. Events: Fosdem in Elsene/Bruxelles on 1./2. Feb. 2025 (info); what next?
   7. Any other business (board members forgot to ask the secretary to put it on the agenda)
3. Question Time

   Questions from CAcert.org community members can be added until beginning of committee meeting! As well questions can be asked at "Question Time", without added question here.

   1. "Question One." added by Your Name Comment: Replace "Question One" by your Question and add your name

1. Closing

1. on hold (for later this year)
   1. Infrastructure: (Dirk)

      1. Start thinking about planning when to do things about new roots, so we are prepared several years in advance, as no certs should have a end-date after any root certificates. Also take a look at the old Escrow article. https://wiki.cacert.org/Roots/EscrowAndRecovery

   2. Remote Assurance (Brian)

      1. Creation of remote assurance sub committee (RASC) on the hold until Eva is available for the policy. Secretary got in touch with Eva on Oct. 12.
         "Users Requests, summarized." added by Aleš a) need for a distant assurance (no assurers, no TTP possibility in their country); b) need for the write access to our Wiki.

1. To remember: Goals 2021/2022 (propositions by board 2020/2021) - Each goal needs a responsible person on the board who keeps an eye on it and reports regularly, keeps in touch with the responsible people. obsolete / started / waiting for available time

   • push OrgA (Guy)
   • expand PR (Alex cannot do this, wants to hand over)

   • delivering the OpenID Connect integration, for which CAcert is funded by the RIPE NCC.

   • expand background check

   • remote assurance, if accepted by the community;

   • simplify the certificate creation (this enables the start of various projects from the pipeline)

   • software development and testing

   • New CSR software

   • support SecureU (find an active board member for them in Germany)

2. Not to forget: Staffing the teams
   1. Applicants to the Infrastructure team
   2. Applicants to the Development team
   3. Applicant to the Critical team

1. Access to local systems for board members

1. Tasks assigned to Board Members and others

1. Software Team

   1. Issue 1502: Adapt the UI at CAcert.org to deal with the "keygen" feature having been removed in browsers (Some of this will be met with 1551 )

   2. Issue 1482: Limit validity period of new HTTPS certificates to one year

   3. Issue 1444: PHP - Brian

   4. Issue 1417: Keygen / new CSR software - Bernhard

2. Organisation Assurance
   1. How to relance OrgA? (Guy)
3. Grant applications

   1. Protopype Fund https://prototypefund.de/en/ (mail to SW Board only)

      1. The Prototype Fund is a project of the Open Knowledge Foundation Germany, funded by the Federal Ministry of Education and Research (BMBF). This is for residents of Germany only. We could create a group of people that work on a project for CAcert (with all support of the others in the background). It runs for two more years, every 6 month.
      2. Infra does not see any acute need at the moment, and does not have the capacity to provide qualified support.
      3. There are some ideas for software, but in infra's view there is still a lot of conceptual and preparatory work missing. What Infra could imagine is financing people to carry out a requirements analysis and write a requirements and test specification. This could then be used as a basis for a new implementation of the CAcert software (WebDB, Signer and perhaps other things like CATS). But these are just a few ideas of JanDD and he cannot currently recommend any people who would be suitable for this. Potential candidates would have to deal intensively with the existing software on the one hand and with the underlying policies on the other, and would have to identify a lot of missing information, ask for it and make assumptions for discussion. This requires very good analytical and communication skills and a high level of stamina.

1. Blockchain

   1. see here: https://wiki.cacert.org/Brain/CAcertInc/Committee/MeetingAgendasAndMinutes/2018-03-01/ideas#Blockchain (waiting for answer from IanG)

Minutes Committee meeting - 2025-03-06

Present, by alphabetical order: Aleš, Brian, Dirk, Etienne, Kim.

Opening

The secretary opens the Committee Meeting at 19:05. The minuts of the last meeting were accepted with 3 yes and 2 abstains (m20250306.1). The committee agrees on the 3rd of April 2025, 18:00 UTC as date for the next committee meeting. (Following dates 8th of May 2025, 5th of June 2025). The committee agrees on the new meeting time 18:00 UTC during DST season for not changing the meeting time in Eastern US and EU.

Business

2.1. OpenID Connet: Dirk and Moinmoin people are tryiing to speed up moinmoin. OIDC will follow. Documentation: Brian.

2.2. CAcert Spain: It should be written 2003 instead of 2023. And organisation instead of company. With this changes, the committee is happy with the letter; it can be sent by the secretary.

2.3. OrgA: Etienne will meet Alex in March.

2.4.1. OpenID @wiki & @blog; more will come -> see 2.1.

2.4.2. Let's Encrypt @wiki & @blog: Let's encrypt for public-facing sites (wiki and blog) has long been desired. It should be noted that these certificates must be replaced every 90 days. Automation is not trivial. JanDD ideas are on the testserver, but OpenID Conect has priority. It will be installed only after client cert login is remplaced by OIDC.

2.4.3. Delete accounts with OrgA and Software repair is done. Firewall 2 is updated and waiting for transport to the Netherlands.

2.4.4. CPS: Dirk will discussed the draft with a former arbitrator (E.S.). Following this talk, the approach is correct. It will be pushed to PolG for discussion. The secretary will write a short introduction. If (1) PolG votes for the new CPS, (2) the committee has too take a decision after that to create the new root certificates. (3) Critical and Software have to implement it then.

2.5. Youth: No information this month.

2.6. Events: CAcert was there at the info desk. Following events: Lucamp and FROSCON.

The president closes the meeting at 19:40.

Motions

• https://motion.cacert.org/motions/m20250130.1 (minutes january) Accepted by 3 aye (Aleš, Brian, Etienne), 1 abstain (Kim) as 7-day-motion.

Actions

• CategoryBoardMinutes