Skip to Content.
Sympa Menu

cacert-policy - Re: [CAcert-Policy] [FIRSTREVIEW] Configuration Control Specification

Subject: Policy-Discussion

List archive

Re: [CAcert-Policy] [FIRSTREVIEW] Configuration Control Specification


Chronological Thread 
  • From: Ian G <iang AT systemics.com>
  • To: Policy-Discussion <cacert-policy AT lists.cacert.org>
  • Subject: Re: [CAcert-Policy] [FIRSTREVIEW] Configuration Control Specification
  • Date: Tue, 21 Feb 2006 14:15:03 +0100
  • List-archive: <http://lists.cacert.org/cgi-bin/mailman/private/cacert-policy>
  • List-id: Policy-Discussion <cacert-policy.lists.cacert.org>
  • Organization: http://financialcryptography.com/

Philipp Gühring wrote:
Hi,

Ok guys. I am missing a consistent and agreed-upon threat model.


I love threat models!  They're so much of a
black hole, you can never be wrong :)

(We are discussing implementation issues with unavailable ressources, but we seem to disagree on the underlying threat models)
So please sketch up your threat models, and let´s try to find to a common threat model, before going into implementation details again.

Ok, perhaps i need to rephrase it:

What scenarios exactly are you fearing regarding the security root key?


Ahhhha!  OK.  Here's where it gets interesting.

My question.

  What happens when the root key is posted on the
  comp.security.crypto.compromised.root.keys group?

That's my question.

iang




Archive powered by MHonArc 2.6.16.

Top of Page