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
SKR requires an attestation service to produce the correct attestation, keys, etc.
Working with the service team I was able to deploy a mock attestation server (which is what they use as well) to record SKR tests.
But it's not a sustainable solution. To support cross-language live testing of SKR, we should find the right set of resources to deploy and automate it such that it becomes part of our test harness.
The text was updated successfully, but these errors were encountered:
cross-language https://skrattestation.azurewebsites.net is a perfectly valid solution for now. I just need to have it managed by EngSys in case I win the lottery, instead of just sitting there in my own repo.
tasks to be done:
Investigate whether this can be a completely static resource. If we pre-generated a token that expires in 30 years, we might get away with just having everything hardcoded and static
Work with EngSys on the proper place for this code - as long as it's managed by them it doesn't matter where it lives
Since the work to support live tests is done, this can be pushed off to the backlog for now
SKR requires an attestation service to produce the correct attestation, keys, etc.
Working with the service team I was able to deploy a mock attestation server (which is what they use as well) to record SKR tests.
But it's not a sustainable solution. To support cross-language live testing of SKR, we should find the right set of resources to deploy and automate it such that it becomes part of our test harness.
The text was updated successfully, but these errors were encountered: