You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a bunch of struct layers inside the SCTFE at the moment, let's simplify this. The first layer of complexity, the protobuf config was removed in trillian-tessera#200. This Issue is a continuation of this one.
ValidateConfig takes a lot of flags as arguments, and validated them. This should probably be move to main.
Right now, it also parses the ExtendedKeyUsage, we might want to move this around.
Then there's SetUpInstance which actually applies some logic on stuff and open the root_pem_file, or parses the oids. Logically, I think that parsing the oids is similar to parsing the ExtendedKeyUsage, so I might group them together.
Also, right now, the Tessera storage cannot be created anywhere else than in SetupInstance because, it needs a signer, and the signer is created in there... because we need a note.Signer for the checkpoint, but not for the SCTs.
Then theres's newLogInfo, and this one is a bit annoying as well because it's the one that as the TimeSource object, which is also used in tests.
The text was updated successfully, but these errors were encountered:
There's a bunch of struct layers inside the SCTFE at the moment, let's simplify this. The first layer of complexity, the protobuf config was removed in trillian-tessera#200. This Issue is a continuation of this one.
ValidateConfig
takes a lot of flags as arguments, and validated them. This should probably be move to main.Right now, it also parses the ExtendedKeyUsage, we might want to move this around.
Then there's
SetUpInstance
which actually applies some logic on stuff and open the root_pem_file, or parses the oids. Logically, I think that parsing the oids is similar to parsing the ExtendedKeyUsage, so I might group them together.Also, right now, the Tessera storage cannot be created anywhere else than in
SetupInstance
because, it needs a signer, and the signer is created in there... because we need a note.Signer for the checkpoint, but not for the SCTs.Then theres's
newLogInfo
, and this one is a bit annoying as well because it's the one that as the TimeSource object, which is also used in tests.The text was updated successfully, but these errors were encountered: