-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
NotDashEscaped: You need GnuPG to verify this message

Index: gpg-policy.wml
===================================================================
RCS file: /remote/accounts/swright/CVS-Repos/www/security/gpg-policy.wml,v
retrieving revision 1.3
retrieving revision 1.4
diff -r1.3 -r1.4
1c1
< # $Id: gpg-policy.wml,v 1.3 2004/04/29 18:09:35 swright Exp $
---
> # $Id: gpg-policy.wml,v 1.4 2005/05/17 13:08:31 swright Exp $
114c114
< 
This is version 1.1:
---
> 
This is version 1.2:
116c116,124
<  
v1.1 - 27 Apr 2004 
---
>  
v1.2 - 17 May 2005 
>      
- Minor typographical corrections.
>      
- Changes in The act of
>        signing : Added the additional option of having a signed
>        key encrypted and mailed to the key owner.
>      
-       href="security/gpg-policy-v1.2-v1.1-diff.html">Differences
>      from v1.1.
>  
v1.1 - 27 Apr 2004
184c192
<    
Used for all other signatures, where I have a stront personal
---
>    
Used for all other signatures, where I have a strong personal
187c195
<        signee outside a keysigning situation.
 
---
>        signee outside a key signing situation. 
201c209
< exceptions will be accepted on larger keysigning parties.

---
> exceptions will be accepted on larger key signing parties.

207,211c215,222
< addresses featured in the user IDs that I was asked to sign. They
< contain random strings and will be encrypted to the public key whose
< fingerprint is printed on the paper.  In the event that the signee
< requires a signature only key to be signed I will require an
< encryption-enabled key that lists the same addresses as the
---
> addresses featured in the user IDs that I was asked to sign.

> 
> 
Either
> 
> 
The emails will contain random strings and will be encrypted to the
> public key whose fingerprint is printed on the paper.  In the event
> that the signee requires a signature only key to be signed I will
> require an encryption-enabled key that lists the same addresses as the
231a243,254
> 
> 
Or
> 
> 
I will sign each User ID on the key separately and email the signed
> key, encrypted to the email address associated with the User ID.  The
> signee (who thus controls both the email address and private key)  is
> then able to upload the signed key to a public keyserver of their
> choice (or not).
> 
> 
NOTE: The choice of signing method will be determined by the
> signee.  An exceptions will be made for larger key signing parties
> where the I will determine the optimal method.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iIwEARECAEwFAkKJ+1tFGmh0dHA6Ly93d3cucGh5c2ljcy5hZGVsYWlkZS5lZHUu
YXUvfnN3cmlnaHQvc2VjdXJpdHkvZ3BnLXBvbGljeS5odG1sAAoJECnyLrRoK0TW
IL0AoLT6OyRpoi+SSYPLEE10iUNFZ7zqAKCZthu04Fmlsu/+ipzcQm49aLOIZQ==
=deS5
-----END PGP SIGNATURE-----