Expose client functions

[cmurphy]

Description

Tessera exposes a client that consuming projects can use to read from the C2SP tiles API. The Static CT read API is just slightly different, and the Tessera client does not work with it. It would be really nice if the TesseraCT client had a public interface so that a CT monitor could use it. With this not available, I'm having to copy significant chunks of the internal client code to write a monitor for TesseraCT (1 2 3 4 5 6 7 8 9)

[phbnf]

We aim to do this later in the year, as part of v1.0 (I'll link this issue on this roadmap, thanks for filing it!). At the moment, we're focusing on the Beta release and launch our own production logs.

I wouldn't want to start exposing a library that we don't have the capacity to support publicly at the moment. Does the library works well enough for now for you use case or do you need more features?

While I'm here:

• IPng friends shared https://git.ipng.ch/certificate-transparency/ctfetch recently (built with sunlight and tlog librairies), which you might find interesting
• I've also got a client tool baking using TesseraCT's internal librairies: https://github.com/transparency-dev/tesseract/pull/556/changes

[cmurphy]

We aim to do this later in the year, as part of v1.0

Great, glad to know it's already on the roadmap.

Does the library works well enough for now for you use case or do you need more features?

No, the library functions are what I need exposed which are all currently buried under internal/.

While I'm here:

Thanks for sharing, those are interesting but in both cases they are providing a binary command when what I need is a library that I can incorporate into an existing monitoring tool.