Freshness on new SGX Processors?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- cryptography, security
Research direction
Start with Intel's linked support article and the cited scalable SGX paper, then compare their claims about AES-XTS and freshness. Done means obtaining an authoritative answer about freshness guarantees on 3rd-generation Xeon Scalable Processors and documenting the supporting source.
Written by the indexing model from the issue text.
Description
Last year Intel announced that their new 3rd gen Xeon Scalable Processor can support up to 1 TB of EPC. I always understood that the small EPC in SGX was due to the need for an on-chip Merkle tree that maintains freshness. This announcement by Intel was accompanied by an explanation saying that they have overcome this scaling issue by removing the Merkle tree/MEE and instead using AES-XTS. I have read a few sources explaining AES-XTS, but have not been able to confirm anywhere if it provides support for checking freshness. Some sources even seem to imply that freshness is not guaranteed anymore, but this could be me reading into certain claims incorrectly. I was hoping to learn more from Intel/get an official source on this because I am having difficulty finding clear information on the subject. Thank you!
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/confidential-computing.sgx
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
intel/confidential-computing.sgx#1100 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
intel/confidential-computing.sgx#1085 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
intel/confidential-computing.sgx#1083 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
intel/confidential-computing.sgx#1078 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
intel/confidential-computing.sgx#1076 ·
All issues in intel/confidential-computing.sgx
Similar issues
-
v3: Lua m.setvar() returns -1 on errors, so the script gets stack garbagePossibly taken A pull request linked to this issue is open or already merged. Open3.x bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
owasp-modsecurity/ModSecurity#3731 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Sendspin/sendspin-cpp-cli#111 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
scp-fs2open/fs2open.github.com#7984 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 4 days
-
core docs p3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
RunanywhereAI/runanywhere-sdks#1199 ·
Maintainers usually reply within 1 day