aws / aws/aws-nitro-enclaves-cli
nitro-cli describe-enclaves not accurate in debug mode
- Dominant language
- Rust
- Stars
- 156
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
When starting an enclave in debug mode, the `nitro-cli describe-enclaves` command prints out the PCR's the enclave is supposed to have based on image creation, instead of the full 0 values which it has in debug mode. I realize that the full 0 values are mentioned in the official documentation, but the command itself is actively misleading when used on debug mode enclaves.
I suggest adding a check which changes the PCR's to the special full 0 values if a given enclave is in debug mode.
Contributor guide
Research direction
Start by tracing the nitro-cli describe-enclaves command's output handling and how it identifies debug-mode enclaves. Verify the current PCR values against a debug enclave, then confirm that the command reports full zero values for debug mode without changing non-debug output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100