oasisprotocol / oasisprotocol/oasis-core
Figure out how to properly sign release enclaves.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
At some point we need to start signing enclaves with our production SGX keys. This isn't too difficult in theory, however the fortanix tooling (sgxs-sign) does not support signatures with a HSM.
As it is unacceptable to be carting around our signing key as a PEM file, this likely will require extending the tooling or writing our own.
Estimated cost: 1 sprint
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, or entry points are named. Start by locating the release-enclave signing flow and the Fortanix sgxs-sign integration, then determine whether extending that tooling or building an alternative is feasible. Done means production SGX enclave signing works with an HSM without exposing the signing key as a PEM file.
Written by the indexing model from the issue text.
Assessment
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100