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.

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

Allow CUnseal to work on ranges #71

Open
davidchisnall opened this issue Oct 3, 2024 · 0 comments · May be fixed by #87
Open

Allow CUnseal to work on ranges #71

davidchisnall opened this issue Oct 3, 2024 · 0 comments · May be fixed by #87

Comments

@davidchisnall
Copy link
Collaborator

Currently, CUnseal unseals only if the otype exactly matches the specified type. Originally, CUnseal unsealed anything in the authorising range. I'm not sure why we made this change. Either version can emulate the other.

The current behaviour can emulate the range behaviour by doing cgettype, csetaddr, cunseal.

The current behaviour can be emulated by doing csetaddr, csetbounds, cunseal.

So far, 100% of uses have wanted the former behaviour and so we end up doing the cgettype, csetaddr dance on every unseal for any sealing type that has a length > 1.

It would be nice if the ISA did the common thing.

nwf added a commit that referenced this issue Nov 15, 2024
@nwf nwf linked a pull request Nov 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

1 participant