I stopped reading the phildev.com article when it insisted on third-party photo ID. The point of keysigning is not to verify a person's right to drive or access to health care, it's to associate a key with the identity you use to communicate. Often, that identity is a persistent pseudonym, intended to avoid the very third-parties that issue photo ID. I've run a few formal and informal keysigning parties. I've written up some instructions at https://sobac.com/wiki/Formal_Keysigning I'd be interested in seeing if it can be adapted it for use in a video or audio conference. --Bob -- Bob Jonkman <bjonkman@sobac.com> Phone: +1-519-635-9413 SOBAC Microcomputer Services http://sobac.com/sobac/ Software --- Office & Business Automation --- Consulting GnuPG Fngrprnt:04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA On April 26, 2020 10:07:35 PM EDT, Rouben via talk <talk@gtalug.org> wrote:
Hi GTA LUG folks,
Do you think it’s doable? Based on instructions here I think these can be adapted for Zoom or similar... https://www.phildev.net/pgp/gpgsigning.html
Also I’m curious to see if/what key signing policies folks here adhere to. Here’s a fairly comprehensive example: http://www.arasca.com/olaf/pgp/policy.html
I brought this up before, but unfortunately found the interest was not quite there, coupled with lack of time to do this face to face in the past, the proposed event never took place. I’m therefore wondering if the current predicament of staying at home and holding meetings over Zoom (or similar platforms) can help rekindle this and make it actually happen.
What do you think?
Rouben