On 5 Feb 2006, at 13:41, Julien Cornuwel wrote: > NextGen$ a ?crit : >> That's the major issue : what to do in case of a key compromission ? >>> I'm sure it can be solved easily ;-D >> Suggestions are welcome :) >> > > I'm not really aware of it but I think it's possible to insert a > special file in the SSK to warn that the SSK is burned, no ?
That is correct - we could have a standard file that, if inserted under an SSK, would indicate that the SSK's private key has been compromised and content under the SSK can no-longer be trusted. The problem is that, to be useful, it would be necessary for nodes to attempt to request this private key whenever they request content in an SSK to be sure that it is safe - this could be time consuming, but would only be necessary under circumstances where a compromise could be really harmful (such as a compromise of the private key used to sign some software). Ian.
