should synthesize empty STHs about certificate-transparency HOT 2 CLOSED

I don't like the "no STH in the database" state at all.

To solve it properly, you have to have a TreeSigner object kicking around, which we might not want to have on frontends (if we were to separate serving frontends and signers). Having them requires further distribution of the log private key, which is one of the reasons brought out for separating the frontends from the signers.

Down the line, I think I'd like it better if frontends would not start serving at all until they found some STH to serve, rather than try to synthesize a fake STH.

PR #148 starts down that road, at first by making sure that there is some valid STH locally (since the frontend and the signers are still intertwined at the moment)...

from certificate-transparency.

This doesn't happen anymore with PR #148 merged in, and @benlaurie agrees that it makes sense to not start serving until we have an STH (no need to synthesize them).

from certificate-transparency.