Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

virt: Add possiblity to run with multiple clients #137

Merged
merged 2 commits into from
Nov 9, 2023
Merged

virt: Add possiblity to run with multiple clients #137

merged 2 commits into from
Nov 9, 2023

Conversation

sosthene-nitrokey
Copy link
Contributor

Motivated by testing: trussed-dev/trussed-staging#11

Example of what is allowed by this PR:

with_ram_clients(["client1", "client2"], |[mut client1, mut client2]| {
    let key = syscall!(client1.generate_ed255_private_key(Location::Internal)).key;
    // The clients are distinct
    assert!(!syscall!(client2.exists(Mechanism::Ed255, key)).exists);
})

@sosthene-nitrokey
Access the keystore via a path rather than the CoreContext
41da790 
Similar to 5af424e, this patch updates
the `keystore` method to be able to create a keystore with a custom path.
This can be useful for backends that want to have a keystore distinct from
the core one.
@sosthene-nitrokey
virt: Add possiblity to run with multiple clients
581219f
@sosthene-nitrokey
Copy link
Contributor Author

Based on #137 for trussed-staging.

@sosthene-nitrokey sosthene-nitrokey merged commit 9763723 into main Nov 9, 2023
2 checks passed
@sosthene-nitrokey sosthene-nitrokey deleted the virt-multi-client branch November 9, 2023 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@robin-nitrokey robin-nitrokey robin-nitrokey approved these changes

@nickray nickray Awaiting requested review from nickray

@daringer daringer Awaiting requested review from daringer

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@sosthene-nitrokey @robin-nitrokey