On 27/05/2012 22:39, Jeffrey Johnson wrote: > On May 27, 2012, at 6:15 AM, Robert J. Hansen wrote: >> >> "We never, never, never lose certificates." > > And what is being discussed is filtering an expired signature, not > a public key, for one specific robo-signer. > > Even if the filtering was solely limited to > an "opt-in" user requested hkp:// extension narrowly limited to just > 0xca57ad7c > expired signatures > there starts to be a benefit to GPG users who otherwise are "cleaning" > imported signatures manually.
Users cleaning imported signatures *manually*? GnuPG users, at least, can simply add the import-clean import-option to their gpg.conf. What warrant do we have for applying any filtering at the servers at all? If the "problem" is one robo-signer, wouldn't it make sense to talk to its minders? -- John Marshall
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/sks-devel
