-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There is a lot of background, for the details please read the thread
about my motion at the February 2008 meeting.
In short I reached a conclusion that we no longer really need to have Meetings as we have them now, with the exception of the Annual Meeting.
For all the other meetings we currently have we'd separate things out functionally.
- Meets and Greets would occur through schedule activities and events held with roughly the same frequency that we currently have meetings.
- Reports and such would be based on time.
- Voting and all procedural matters would occur through a cryptographically secured process.
It's that last one that seems to have the most confusion, so I'd like to cover it in more detail, and answer questions about it. However I was told that the issue should be separated from the motion and have thus created this instead.
You might think that it's complex, and in reality the details that matter are. However actual day to day use of it is very similar to what we already do, and things we're already quite able to do.
You might also think that it requires expensive software. Everything I'm using to post this, create this, and even to digitally secure my message, are in fact, completely free. 100% free. I paid nothing for it, it's totally legal, and I can even see the source code with a tiny bit of effort (downloading some additional things). Similar solutions exist for Windows, Mac OS, etc.
Next, you might wonder why there is this strange bit of text around my message?
Well, if you 'quote' me, and copy everything that's between the end of the [ quote ] start, and the [ /quote ] end, you can then use one of the programs referenced in the other thread, and the attached public key (As of yet, no one has 'signed' it signifying that it's been validated to represent me. I can explain that later.) to check that this message was in fact signed by the matching private (secret) key that only I keep.
Programs that work with these keys typically secure them by scrambling them (not the proper term, but probably the closest term for anyone reading about cryptography for the first time here) based on a password that is asked for each time you want to sign something or encrypt something with it. That is, this is based on something you have (the private key) and something you know (the password).
Signing something with these programs means that they run a special math problem over it, which produces a short summary number. Then your private key is used to alter that number in a way that can be verified by the public key. In that way, anyone else can use the same formula, then check the result by trying to decode your signature with the public key. If they match, then the information is the same as the information the signing party saw. (Technically since it's a reduction there could be more then one message that produces the same result, however the odds of that message actually looking like a valid message are astronomical. The math problems generally also use a few other tricks to raise the odds of this even higher.)
By using these tools it's possible to build different things.
1) Establishing a relationship between a given Public/Private key pair and a Person.
2) Verifying that clear text (like this post) messages were signed by that Person and unaltered since. (Like this one)
3) By using the Public key, ensuring messages are sent so that only the proper user with a Private key may decode them.
Here are some links to software that the average user may find easy enough to use under various operating systems...
Windows:
http://www.gpg4win.org/ (the guide is towards the end of that short list at the top left)
OSX:
MacGPG with?
GPG toolsLinux: Please Google/etc the following terms to get a guide for your distribution. Name-of-your-distribution(EG Ubuntu) kgpg OR seahorse
(So for ubuntu, you might google: ubuntu kgpg OR seahorse )
Multi-OS:
http://www.media-art-online.org/wija/ (This -might- work... if it does it looks like it supports other operating systems too. It looks like it may be slightly more difficult to find a good user interface for GPG for the mac, but one should exist somewhere.)
For use with Firefox see
FireGPGGeneral information
http://en.wikipedia.org/wiki/GNU_Privacy_GuardAnd of course, the background mentioned at the top of this (see that thread).
Note: Edit #3, trying to figure out why it failed to verify...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHtU8LNtNlwzbQFW0RAoTiAJ4qEJIye73H7qzaiLlpxyq7MAx8RgCcCtdQ
j/MUMwOMqGXqU/qUiD5R1w0=
=MyL4
-----END PGP SIGNATURE-----