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
{{ message }}
Repository navigation
Commit 4f275d1
Browse filesBrowse the repository at this point in the historyBrowse files
fix(stack-encrypt): address the review of CipherRef
- The rustdoc on CipherRef named every entry point that runs through a
cipher. It now names the ones that take it: the decrypt entry points
and the Pending constructors. It says that an encrypt entry point takes
a KeysetCipher, and that a CipherRef lives as long as the connection.
- The CHANGELOG entry lists every changed function. It says that an owned
KeysetCipher is now accepted, that a pending through a temporary keyset
handle now compiles, and what to write in place of a CipherScope bound.
- CipherRef has one accessor for the keyset, keyset_id(). Its Debug
output names the field keyset_id, as KeysetCipher's does.
- Functions that only forward the argument no longer convert it first.
The private collect_releasing and decrypt_through take a CipherRef.
- New tests: an owned KeysetCipher refuses a foreign leaf before any key
is retrieved, and opens its own; a pending outlives a temporary keyset
handle; the guest's scope_for gives the right keyset for each selector;
and a compile-fail case pins the "consider borrowing" hint for a
StackCipher passed by value.
- CONTEXT.md is rewrapped and names the owned KeysetCipher. The plan's
tracking line says that #1120 is closed and #1504 is merged.
0 commit comments