ratsd client libraries

[ionut-arm]

Hi all, I'm hoping to use ratsd as a backend for our Exported Authenticators-based attested TLS prototype. Are there client libraries available for ratsd, or is that even on the "roadmap" of the project?

In particular, I'd be keen on a Rust client library, even if it's just a thin wrapper around some REST calls for now :)

[cowbon]

Hi @ionut-arm , Ratsd currently provides only the Restful APIs to get an evidence of the platform. A Rust-specific wrapper to make HTTP calls to ratsd is unavailable.

[thomas-fossati]

Yeah, that's what I had assumed! Do you think new client libraries would go into a new repo?

Hi @ionut-arm, I think so. That’s how we usually handle it in Veraison — take a look at veraison/apiclient and veraison/rust-apiclient. However, I'm not sure I understand how you would use it in a context where the RATSD attester is the aTLS endpoint.

[ionut-arm]

I'm not sure I understand how you would use it in a context where the RATSD attester is the aTLS endpoint.

How so? Is it meant to be used and consumed from a different environment?

I think my mental model of RATSD was that it was similar in nature and intent to Parsec, which was intended to run in the attester for the use of all software that can access its API.

[thomas-fossati]

I believe that the aTLS endpoint needs to sit alongside RATSD, in the same confidential VM. Correct?

If so, you would use the RATSD API locally (e.g., via the loopback interface).

[ionut-arm]

Ah, yes, correct, but I'm guessing there's a need for a client that handles that too?

[thomas-fossati]

yes, if you want to go through RATSD (as opposed to talking directly to the attesting environment).