search

ku-sldg / attestation-testbed

BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Verify PK utilization ONLY after acquisition #43

Open Durbatuluk1701 opened 4 months ago

Durbatuluk1701 commented 4 months ago

The method developed for Private Key utilization and acquisition must ensure that a private key is acquired before being utilized. This may seem rather obvious, but we want a soft landing to occur if utilization is attempted before acquisition

LoganSchmalz commented 1 month ago

Original use case: PK-acquiring ASP would check if a key is available and if so (re)direct AM to a particular signing ASP to utilize the key, otherwise the PK-acquiring ASP would return an error. (This explanation was commented out from the "Attestation Manager Interfaces" wiki page due to current uncertainties.)

More simply, the signing ASP itself could return an error if it cannot use its key. Thus, we are reconsidering whether also having the PK-acquiring ASP simplifies anything or adds value compared to only using a signing ASP. One benefit it may provide is having a more explicit mechanism for an AM to know if a key is unavailable for use (though I think we need to justify the practical uses for this, like figuring out what benefits this mechanism would actually provide in an attestation process, and we need to determine whether this is equally possible without PK-acquiring ASPs).

This will likely be closed as not-planned after re-investigating/documenting the signing ASP interface.