May 20th, CAcert has started the Software-Testers Reward Challenge 2011
The second result for June 2011 now has counted:
Continue reading
May 20th, CAcert has started the Software-Testers Reward Challenge 2011
The second result for June 2011 now has counted:
Continue reading
The Software-Testers Reward Challenge 2011 is now running the last two days. So its your last chance to climb into the hall of fame.
The Software-Testers Reward Challenge will end Thursday, June 30th at midnight.
The software tester with the highest count of reports written related to the listed bugs under the Tester Portal receives a reward of 30 Euro. The 2nd one a reward of 15 Euro.
Each report under the listed bug numbers counts 🙂
Since Tuesday we have at least two new bugs added to the testserver that you can start testing:
Happy testing
You may have received an automated mail by CAcert today or yesterday evening, stating that one or more of your certificates are unsafe and will be revoked soon.
I don’t want to go into more technical details before the relevant certificates have been revoked, if you received one of those mails some technical details are included there. Please do not use the listed certificates any more and replace them with newly issued ones as soon as possible.
New signatures for CAcert-Class 3-Subroot-certificate – Changes for users of CAcert-Certificates
(english version, german see below)
CAcert re-signs its Class 3-certificate with a new SHA256 signature. The formerly used MD5 signature is not seen as fully secure any more by Mozilla and is therefore deprecated. Mozilla is going to drop support for MD5-signed Class 3-subroot and end-entity certificates after 30th June. Users of Mozilla products like Firefox, and Thunderbird may experience errors when these programs try to verify such certificates.
Hence webmasters, as well as users of CAcert’s Class 3-certificates, have to download and install the newly signed certificates from CAcert’s website. The same procedure applies if the Class 3-certificate is used for secure e-mail communication, for code signing, or for document signing.
The procedure in short:
1. Download the new Class 3 PKI Key from http://www.cacert.org/index.php?id=3
2. Either install it directly in your browser, or any other client program you use the certificate for, or save it to the SSL configuration directory of your webserver. For Apache this may be: /etc/apache2/ssl/class3.crt (PEM-Format)
3. Verify the SHA1-fingerprint of the downloaded certificate:
AD:7C:3F:64:FC:44:39:FE:F4:E9:0B:E8:F4:7C:6C:FA:8A:AD:FD:CE
Example Commandline: openssl x509 -fingerprint -noout -in class3.crt
Or look at the fingerprint when importing the certificate into the webbrowser
4. Webmaster now re-create the necessary hash with c_rehash, or the like
By using the safe SHA256-hash CAcert is focussing on securing the internet on a continuing basis. Further information is given on CAcert’s Wiki page.
-+-
Neue Signaturen für CAcert-Class 3-Subroot-Zertifikat – Änderungen für Nutzer von CAcert-Zertifikaten
CAcert signiert sein Class 3-Subroot-Zertifikat neu mit einer SHA256-Signatur. Die bisherige von CAcert genutzte MD5-Signatur wird von Mozilla als nicht mehr ausreichend sicher angesehen. Mozilla wird deshalb MD5-signierte Class 3-Subroot- und End-Zertifikate nach dem 30. Juni nicht mehr unterstützten. Benutzer etwa von Firefox und Thunderbird können nach diesem Tag einen Fehler beim Prüfen MD5-signierter Zertifikate erhalten.
Webmaster wie Webbenutzer müssen daher, wenn sie das Class 3-Subroot-Zertifikat verwenden, dieses neu von der CAcert-Webseite herunterladen und installieren. Gleiches ist erforderlich bei Verwendung der Class 3-Zertifikate für sichere E-Mail-Kommunikation, zur Code-Signierung oder zum Unterzeichnen von Dokumenten.
Der Ablauf in Kurzform:
1. Den neuen Class 3 PKI Key von http://www.cacert.org/index.php?id=3 herunterladen
2. Je nach Anforderung entweder direkt im Browser bzw. anderen, benutzten Programmen installieren oder in das SSL-Konfigurationsverzeichnis des Webservers ablegen. Für Apache zum Beispiel: /etc/apache2/ssl/class3.crt (PEM-Format)
3. Den SHA1-Fingerabdruck des heruntergeladenen Zertifikats prüfen:
AD:7C:3F:64:FC:44:39:FE:F4:E9:0B:E8:F4:7C:6C:FA:8A:AD:FD:CE
Beispiel Kommandozeile: openssl x509 -fingerprint -noout -in class3.crt
Oder im Web-Browser Anzeige des Fingerprints beim Zertifikatsimport
4. Webmaster erzeugen dann den erforderlichen Hash mit c_rehash oder ähnlichen Programmen neu
Durch den nun verwendeten SHA256-Hash investiert CAcert weiter in ein sicheres Internet. Weitere Informationen befinden sich im CAcert-Wiki.
May 20th, CAcert has started the Software-Testers Reward Challenge 2011
The first result for May 2011 now has counted:
Continue reading
CAcert.org is scheduling ATE’s in the United States this summer.
Dear CAcert Supporters,
To become Audit Ready, CAcert is heavyly depended on a working Software-Assessment team.
The Software-Assessment team is depended on an active Software-Testteam.
Continue reading
On the 12 May 2011 the NLUUG (Netherlands Unix Users Group) will hold its semiannual conference in De Reehorst, Ede.
The topic is “Open is Efficient”.
CAcert will have a booth there.
Are you interested and willing to help out at the booth please contact me and/or sign up on the CAcert wiki – http://wiki.cacert.org/events/vj2011
Remember Assurers must have passed the Assurer Challenge!
Be sure to enlist as assurer on the event page.
For more information on the conference:
http://www.nluug.nl/activiteiten/events/vj11/index.html
We’ve just started our this years Easter Egg Challenge … We’ve put a couple of patches on to our testserver CACERT1 for you, our fellow and our new Software testers. We’ve put light to heavy patches to the package so everybody is able to walk thru the testserver web pages and search our Easter Egg’s.
Continue reading
A new default rule has been added to Practice On Names – Hyphen Rule.
For the purposes of checking the Name against PoN, a hyphen in given names is to be treated as optional.
Continue reading