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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: