[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgp-keyserver-folk
Subject:    RE: Do keyservers honor the no-modify flag?
From:       "Harmon, Randy" <rjh () pgp ! com>
Date:       2001-03-01 8:54:27
[Download RAW message or body]

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Er, the complication should be the exception I mentioned.  Late night
;)

Randy

- ------
Randy Harmon
administrator, keyserver.pgp.com
engineer, PGP server team
rjh@pgp.com
 

> -----Original Message-----
> From: Harmon, Randy [mailto:rjh@pgp.com]
> Sent: Thursday, March 01, 2001 12:50 AM
> To: 'Brian M. Carlson'; pgp-keyserver-folk@flame.org
> Subject: RE: Do keyservers honor the no-modify flag?
> 
> 
>  
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> There is some experimental support at keyserver.pgp.com, where the
> keyserver will require a signed operation (same result as when we
> get an unsigned delete request) if the version already on the
> server
> contains that flag.  I don't think the RFC discusses this issue,
> but it makes sense that this should be an exception to the
> no-update-allowed rule.
> 
> One complication is that signature revocations should be honored
> when uploaded by third parties, and are not.  Another is that our
> client software doesn't yet have a user interface to set this flag,
> due
> mostly to the maturity issue.
> 
> Randy
> 
> - ------
> Randy Harmon
> administrator, keyserver.pgp.com
> engineer, PGP server team
> rjh@pgp.com
>  
> 
> > -----Original Message-----
> > From: Brian M. Carlson [mailto:karlsson@hal-pc.org]
> > Sent: Wednesday, February 28, 2001 8:41 PM
> > To: pgp-keyserver-folk@flame.org
> > Subject: Do keyservers honor the no-modify flag?
> > 
> > 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > 
> > This message was forwarded from comp.security.pgp.discuss:
> > 
> > > Do any currently running key servers honor the "no-modify" flag
> > > (key server preferences, subpacket type 23; see RFC2440, sec.
> > > 5.2.3.16)?  
> > > 
> > > This flag, if I understand it correctly, is supposed to prevent
> > > (or at least discourage) modifications to a version-4 key by 
> > anyone other
> > > than the key owner.
> > > 
> > > Rich Wales         richw@webcom.com         
> > http://www.webcom.com/richw/
> > > PGP 2.6+ key generated 2000-08-26; all previous encryption 
> > keys REVOKED.
> > > RSA, 2048 bits, ID 0xFDF8FC65, print 2A67F410 0C740867 
> > 3EF13F41 528512FA
> > 
> > - -- 
> > Brian M. Carlson <i.am!BK2204>
> > PGP Key: 0x560553E7
> > Website: http://i.am/BK2204
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.0.4 (GNU/Linux)
> > Comment: For info see http://www.gnupg.org
> > 
> > iQEVAwUBOp3S9+WR/8lWBVPnAQGXPQf9EWkjI76E87Na03RRL+jFtlf5G5T/qx5m
> > 2HR0iaG7Mz/oJGqkUX/PmD0Rl6g9Z3WFgumWsczntJMRbzjH4s5DtsojU0rRrAmw
> > 3Lr4KJF4/KuIqfnIEM3LIg17LrIngXgB1Xo+fumd5Ag8jsqikq2AwnmmLfsU1HEL
> > hIw5WyHm3coC7RiUwkCHo2eof5oAhvAlbjmdWRieodvPymTB9kqWCtHm2lljg8cv
> > rmTk8RRb76MiDaGILliBcA6/zegeRgzP7F7trJ0swfiZY3OauwtSVwD8O5nqswfh
> > pkCo/mT1uGXSAmE0c5XbhY0FitW9AJKE3eRdVbBtSvA/oxGrNqYa/Q==
> > =6Oy4
> > -----END PGP SIGNATURE-----
> > 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGP 7.0.1
> 
> iQA/AwUBOp4OtFy3t/KgqlweEQI7iwCcDqO++ZATlemtCyXM7sWOreR3/CsAn0ua
> gOW/TQefw0hBEDl6f4zkwH6T
> =Pgjt
> -----END PGP SIGNATURE-----
> 

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.1

iQA/AwUBOp4P1Vy3t/KgqlweEQJzfwCgzZq328gejaKAT7+uFXqXcgMgi4gAn2Ic
qtfnyqfoVI9VgsIQV8lIFfiq
=nMIF
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]