Add sancus_untag functions and fix sancus_unwrap_with_key
#37
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gianlu33
commented
Oct 8, 2021
src/sancus_support/sm_support.h
Outdated
| } | ||
|
|
||
| // compare MAC with provided reference `tag` | ||
| return constant_time_cmp(tag, computed_tag, SANCUS_TAG_SIZE) == 0; |
There was a problem hiding this comment.
@jovanbulck would this comparison be a security issue as well?
There was a problem hiding this comment.
yes good point,it might, so better to avoid this. Since the function already returns an int, no need to do this comparison to zero.
I changed the order of these functions so that we could call `sancus_untag_with_key` inside sancus_`unwrap_with_key`. To do so, the former needs to be declared before the latter
Normally, `sancus_unwrap_with_key` always fails if cipher_len is zero. This commit solves this issue by leveraging `sancus_untag_with_key`
gianlu33
force-pushed
the
sancus-untag
branch
from
af7a2be
to
666f960
Compare
jovanbulck
reviewed
Oct 20, 2021
jovanbulck
reviewed
Oct 20, 2021
jovanbulck
approved these changes
Oct 20, 2021
jovanbulck
reviewed
Oct 20, 2021
|
Merged, thanks @gianlu33 ! 👍 |
gianlu33
pushed a commit
to AuthenticExecution/sancus-compiler
that referenced
this pull request
Nov 4, 2021
Add `sancus_untag` functions and fix `sancus_unwrap_with_key`
gianlu33
pushed a commit
to AuthenticExecution/sancus-compiler
that referenced
this pull request
Nov 5, 2021
Add `sancus_untag` functions and fix `sancus_unwrap_with_key`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements what discussed in #36 and fixes (in sw of course) the bug mentioned in sancus-tee/sancus-core#26.
About the constant-time comparison function, I basically copied the NaCl function referenced in #31. However, I didn't really understand why they use this logic in the return statement:
Is there a specific reason for this logic (I mean, in terms of security)? Can't this be simplified to something like
return d == 0?I also had to move
sancus_tagandsancus_tag_with_keyup in the file. The reason is because I added a call tosancus_untag_with_keyinsidesancus_unwrap_with_key, therefore the former needed to be declared before the latter.Edit: I just read what @jovanbulck wrote in #31, so that logic in the
returnstatement is to avoid having an if branch. Good!