commoncriteria / commoncriteria/authserver
EAP-TLS mutual authentication and directionality
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Our understanding is that the RFC for EAP-TLS requires mutual authentication, so we propose modifying the Module to mandate the relevant mutual authentication SFRs.
For the interface between the TOE and the NAS, is there a standard direction that the connection will always go (e.g. does the NAS as a client initiate an EAP-TLS connection with the TOE as the server, or does the TOE as a client open a persistent EAP-TLS channel to the NAS where the NAS is the server)?
The answer to this will determine whether we need to mandate FCS_TLSS_EXT.2, FCS_TLSC_EXT.2, both, or either.
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
Review the EAP-TLS RFC and the Module's relevant mutual-authentication SFRs, then resolve whether the NAS or TOE initiates the connection. Done means documenting the directionality and deciding whether FCS_TLSS_EXT.2, FCS_TLSC_EXT.2, both, or either must be mandated.
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