[TriLUG] CAcert Events
bdmc at bdmcc-us.com
Mon Feb 20 09:09:03 EST 2012
Joe Mack and I have been having an out-of-mailing-list conversation over the week end, and he brought up some points that I thought should be part of the mailing list.
His understanding was that we were talking about a closed, perhaps private, event, only for those who were already CAcert Assurers, and that others were not welcome.
The truth is far from that. What we are discussing is a pair of events, to take place on two days, the regular Thursday evening TriLUG meeting, and the following Saturday morning, as long as that suits the majority of the attendees.
The TriLUG meeting is for an overview, background and education. I have updated the Agenda on the wiki page to provide a bit more information, although there is much more that needs to be added as we understand the needs of the TriLUG audience better. We expect to discuss the concepts of PKI ( Public Key Infrastructure ), X.509 certificates, particularly as they compare to PGP and GPG, and some information about CAcert, including history, purposes and policies.
The ( very incomplete ) Agenda can be found at https://wiki.cacert.org/events/ATE-Raleigh and will continue to be updated.
Even the ATE, the Saturday event, is open to anyone who would like to attend. The expectation is that you will leave as a CAcert Assurer, but that is not a requirement. Anyone who would like to join us on Saturday and is interested in a much more in-depth course on what a CAcert Assurer is and how to become one, is welcome to join us. I only ask that you notify us of your intention to attend, so that we can arrange for an appropriately-sized venue.
One possible result of these sessions is to create a sort of North American center for CAcert, one of several places in the world that are populous enough to be both self-sustaining and provide seeding for other areas near and far. For instance, if your work causes you to travel to different parts of the country, the continent or the world, you can then offer to Assure people at your various destinations, helping them to grow their own population of CAcert Community Members and Assurers.
A major, if not the primary, goal of CAcert over the past few years has been to be accepted and incorporated within the major browsers.
Unfortunately, without an expense somewhere on the other side of $100,000, most of them will not automtically accept the CAcert Root Certificate. It is a rather closed club, and an Open Source player is not welcome.
That is part of what Cristobal and I and others have discussed in prior TriLUG meetings on this subject.
I am sure that I have missed critical items or details, so please feel free to raise questions, as Joe did.
More information about the TriLUG