commoncriteria / commoncriteria/authserver
PSK handling in RadSec
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
FCS_RADSEC_EXT.1.3 lists PSK cipher suites as selectable, with an app note to include at least one of them if support for PSKs is selected in FCS_RADSEC_EXT.1.2. We already have FCS_RADSEC_EXT.2 as a selection-based requirement for when the TOE supports PSKs. Rather than have a selection that could be null in a mandatory SFR, our recommendation would be to add a new element to FCS_RADSEC_EXT.2 and put the selection for PSK-based cipher suites in there. That way a TOE that does not support PSK won't have to worry about filling that selection out with a null value. Is this acceptable?
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
Start by comparing the PSK selections and conditions in FCS_RADSEC_EXT.1.2, FCS_RADSEC_EXT.1.3, and FCS_RADSEC_EXT.2. Review how the requirements handle selection-based support, then determine whether the proposed new element resolves the null-selection concern; done means reaching and documenting an accepted specification decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100