Skip to content

Fix typo #43

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

Merged
jeremysinger merged 1 commit into from
Apr 16, 2026
+1 −1
Merged

Fix typo #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion faq/how_to_seal.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ unseal the capabilities we pass to these untrusted functions. For example:
[untrusted func] read as char *: Shh! This is a secret!


To address this potential security issue, we can create our own sealer, and seal sensetive
To address this potential security issue, we can create our own sealer, and seal sensitive
capabilities with it instead of the OS canonical one. The reason for doing so is that, in
CHERI, a sealed capability can only be unseal with its original sealer.

Expand Down