Today we had been informed about an issue with client certificates issued on or after December 20, 2023 being used for login to www.cacert.org.
We did immediately switched off the login to www.CAcert.org for investigation.
We just activated the Username/Password-Login again, but keep the certificate login closed until the issue is resolved.
We will give an update with more details and plan to active certificate login again as soon as the issue is fixed.
A typical message from an user: “Certificate renewal in state ‘pending’ for days. How to remove/renew then?”
Don’t worry, there is a solution (and the reason is independent from CAcert). Please follow the steps as described in the wiki: https://wiki.cacert.org/FAQ/CertCreationRenewalStucks
Deutsch: Wenn die Zertifikatserneuerung in der Endlosschleife endet: Es gibt eine Lösung: https://wiki.cacert.org/FAQ/CertCreationRenewalStucks/DE
Français: Si le renouvellement de certificats dure des heures, voir des jours: voici la solution: https://wiki.cacert.org/FAQ/CertCreationRenewalStucks/FR
català | castellano | ?esky | español | italiano | ??? | nederlands | polski | português | ??????? | svenska | ??????????
Fortunately, there are always users of our services who show their appreciation and contribute to the operating costs. There are various ways to do this, which we would like to point out once again – above all, that sometimes things change over time.
| CAcert Inc CH-7514 Sils/Segl IBAN: CH02 0077 4010 3947 4420 0 Graubündner Kantonalbank, Chur Clearing 774 BIC (SWIFT) GRKBCH2270A | |
 50 EUR |  100 EUR |
 20 EUR |  10 EUR |
DEUTSCH Es gibt glücklicherweise immer wieder Nutzer unserer Dienste, welche sich erkenntlich zeigen und sich an den Betriebskosten beteiligen. Dazu gibt es verschiedene Möglichkeiten, die wir gerne noch einma aufzeigen – vor allem auch, das sich im Laufe der Zeit auch manchmal etwas ändert.
FRANÇAIS Il y a heureusement toujours des utilisateurs de nos services qui se montrent reconnaissants et participent aux frais d’exploitation. Il existe différentes possibilités que nous aimerions vous présenter, surtout parce que les choses changent parfois au fil du temps.
Dear friends and members of the CAcert community. Are you curious and want to know what is wrapped in the package under the tree? This year, Father Christmas has packed something really nice.
As always with CAcert, you can unwrap it faster and enjoy it more quickly if you help out a little. Translate a little. Or do a little programming. Or test a few new functions. Or like this. To do so, you find further information on the web or write to our secretary.
In Wednesday another visit at the datacenter took place, where we installed the updated webdb1-machine to the rack.
There are still some minor issues left (e.g. language selection for main website, automatic mails), which will be activated again remotely withins the next days.
This time the available time on critical teams site was blocked by some investigation issues (e.g.: What caused the outage, why did the internal routines and raid did not work) and non CAcert-related issues (as we all have a family and job, which are time-consuming as well) and and outage of usable internet-connection on critical teams site.
Naming this: If you’re living next to or in Netherlands and want to give us a helping hand for infrastructure and (possible) critical team feel free to contact us via support.
On 7 December, the committee of CAcert Inc (also known as “board”) was constituted as follows:
Two weeks earlier, the board had already discussed organisational issues in depth at a closed meeting. It is aware that collaboration via virtual channels does not only bring advantages. In order to meet these high demands in the future, the committee will continue to address these issues in the coming weeks. Last autumn, those responsible were introduced to the topic by a management consultant specialising in non-profit organisations, who thankfully did this pro bono.
At the Annual General Meeting 2022/2023 of our Geneva based operating association CAcert Inc on November, 11th, 2023, the members of CAcert Inc elected a new committee (also known as “board”). Some familiar faces are still involved, complemented by new blood from Bohemia. We can announce the constitution at the beginning of December.
As a result of a chain of technical failures of old equipment already scheduled for replacement, there are currently certain limitations in the services provided to members of the CAcert community. We regret this terribly.
Mid september, we discovered that a partition contained a corrupt file system. A
subsequent hardware test showed that one of the hard drives was reporting hardware errors. In order to be able to continue using the system, we have moved this partition to a second drive.
Since the end of september the system no longer responds. We suspect that other partitions are defective. Neither web access nor SSH access work, so the only way to find the error can only be analysed in more detail by a visit to our data centre.
In order to still be able to offer as many services as possible to the CAcert community until the repair, we redirected the connections for www.cacert.org and secure.cacert.org in the incoming firewall to the second system. As a result of ongoing hardware renewal, however, this fall-back level is not quite complete: There is no working signer and no up-to-date copy of the CAcert database attached to this system.
That is, why the main page can be used as a start for informing our users about the blog for now, while certificate issuing and WoT access has to be postponed until our technical volunteers have made the several-hour trip to the data centre for troubleshooting. As they are doing this in their spare time and at their own expense, we are very grateful to these volunteers that they will probably be able to do this in mid-October.
If you would like to know what you can do yourself to ensure that such interruptions occur less frequently and are resolved more quickly, read this!
DEUTSCH: Infolge einer kaskadierten technischen Störung sind zur Zeit leider nicht alle Dienstleistungen übers Netz abrufbar. Alle Fernwartschritte haben unsere technischen Freiwilligen bereits unternommen. Bis zu einen Vororteinsatz im Rechenzentrum im Ausland voraussichtlich Mitte Oktober ist der Zugriff auf den Signer und die Datenbank nicht möglich. Wir bedauern dies sehr. Was Sie tun können, um solche Ausfallzeiten künftig zu verringern, lesen Sie hier!
FRANÇAIS: Suite à une panne technique en cascade, tous les services ne sont malheureusement pas accessibles en ligne pour le moment. Toutes les démarches de télémaintenance ont déjà été effectuées par nos volontaires techniques. L’accès au Signer et à la base de données est impossible jusqu’à une intervention sur place dans le centre de calcul à l’étranger, probablement mi-octobre. Nous le regrettons vivement. Vous pouvez lire ici ce que vous pouvez faire pour réduire ces temps d’arrêt à l’avenir!
PORTUGUÊS: Devido a uma falha técnica em cascata, infelizmente nem todos os serviços estão disponíveis pela rede no momento. Todas as medidas de manutenção remota já foram tomadas por nossos voluntários técnicos. O acesso ao signatário e ao banco de dados não será possível até uma visita no local ao centro de dados no exterior, provavelmente em meados de outubro. Lamentamos muito o ocorrido. Leia aqui o que você pode fazer para reduzir esses períodos de inatividade no futuro!
ESPAÑOL: Debido a un fallo técnico en cascada, lamentablemente no todos los servicios están disponibles actualmente a través de la red. Nuestros voluntarios técnicos ya han tomado todas las medidas de mantenimiento a distancia. El acceso al firmante y a la base de datos no será posible hasta una visita in situ al centro de datos en el extranjero, probablemente a mediados de octubre. Lo lamentamos mucho. Lea aquí lo que puede hacer para reducir estos tiempos de inactividad en el futuro.
Some of our community members (users) get a problem while they try to renew an existing certificate. The issue is: Certificate renewal is pending for days/weeks.
First of all, CAcert is not a service provider or a company, but a community. We are all in the same boat. We can only achieve our goals together, with your the cooperation of all of us (of all users=members).
One of our volunteer support engineers, a retired gentleman somewhere in Bohemia, wrote, after he watererd the flowers in the garden:
1. Many users use CAcert without any assurance. Until now, their CSRs were signed by Class 1 Root (–> serial # 1xxxxx) and their CSRs/renewals are stuck in a queue now.
2. These users know absolutely nothing about existence Class 1 & Class 3 Roots, as they don’t remember installing root(s), and when creating a new cert, they cannot see the choice Class 1/3, because with <50 assurance points (trust points) it isn’t displayed.
3. Many users do not know about the existence of Wiki, bugs, blog, CATS… websites. Our education possibly fails in this direction.
And from Alsace, a baker who is also CAcert volunteer writes after putting the children to bed: There is a lot of information and many tutorials are at the FAQ at https://wiki.cacert.org How to create a certificate can be found at: https://wiki.cacert.org/HowTo/ClientCertCreate/
Another help message was sent by a CAcert volunteer who works as a bus driver from his mobile phone during the short break at the terminus: To get assurance points, the easyest way is to meet with two (or three) experienced assurers who can then credit you with the assurance (trust) points you need (you need 50 and get 10-35 per assurer). When you are on cacert.org in your account, go to the Web Of Trust: https://www.cacert.org/wot.php?id=12 (here you can enter your town and search for assurers in the area) or: https://www.cacert.org/wot.php?id=1 (here you can click through to choose from about 6000 assurers worldwide).
Thank you very much to all our active community members who helps here and there and gives other community members a hand. Even very little help is helpfull. If e.g. each of the 6000 assurers from the assurer directory helps with something small for 10 minutes per month, that is already 1000 hours of work. That would solve (almost) all problems. Here is how you too can give your CAcert community a hand: https://wiki.cacert.org/engagement
And another volunteer from Sweden points out, that the issue will not go away till the interface is fixed, which is a work that has been started, but not finished. Furthermore, renewing old incorrectly signed certificates will never work again, as we have said we will not fix the broken code for that, as no certificates should ever have been signed that way. We can’t continue signing them incorrectly.
Wenn die Sommerhitze unerträglich wird, dann ist es höchste Zeit, sich an den Gestaden des Rheins etwas zu erfrischen. Und was liegt näher, als darauf ennet dem kühlen Nass seine Schritte nach St. Augustin zu lenken, wo die Freiwilligen von CAcert an der FrOScon etwas absolut Neues persönlich vorstellen?
