Conceivably you could also fix this by having all verifiets special case this one certificate in their verification software to substitute the correct hash?
Obviously that's a huge pain but in theory it would work?
Obviously that's a huge pain but in theory it would work?
This is not the first time a log server had to be removed due to a failure, nor will it be the last. The whole protocol is designed to be resilient to this.
What would be the point of doing something besides following the normal procedures around log failures?