WebAssembly / WebAssembly/wasi-crypto
Context-Based Security
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 180
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
There are a number of functions which take no context as input. I think I have caught all of them:
options_opensecrets_manager_openkeypair_generatekeypair_importpublickey_importsecretkey_importsignature_importsymmetric_key_generatesymmetric_key_importsymmetric_state_open
These functions do not align with the general strategy of context-based security as used in other WASI specifications. All WASI functions should have some context object (i.e. handle) which is either provided by the runtime or derived from a handle provided by the runtime.
One suggestion for this handle might be a policy handle which allows the runtime to define which algorithms are permitted.
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
Review the listed functions—options_open, secrets_manager_open, keypair_generate, keypair_import, publickey_import, secretkey_import, signature_import, symmetric_key_generate, symmetric_key_import, and symmetric_state_open—and compare them with context-based security in other WASI specifications. Define the required context or policy handle design and how it applies to every listed function; done means the API consistently provides the required runtime or derived context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100