commoncriteria / commoncriteria/fileencryption
FPT_KPY_EXT.1 and MDF
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
I would actually think this should probably have a required choice for stored keys when paired with the MDF in that the "the plaintext key is stored in the underlying platform's keystore as specified by FCS_STO_EXT.1.1" selection would be required when paired with the MDF. It would seem odd to expect the keys to be stored elsewhere when in a configuration with the MDF as the base and not the App.
I guess there could be an option for something like a smart card, though I'm not sure if the key is stored there or if the card would be used to unlock (decrypt) the key stored in the keystore.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files or tests are named. Review FPT_KPY_EXT.1 alongside the MDF and FCS_STO_EXT.1.1 selections, then clarify the intended stored-key requirement and whether alternatives such as smart cards are in scope; done requires an agreed protection-profile change.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100