Upgrade to use authenticated web socket protocol
Open
Nobody has claimed this yet.
enhancement
security
- Dominant language
- TypeScript
- Stars
- 153
- Forks
- 46
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
This needs to be done in conjunction with NSS being upgraded to allow (and check if sent) authentication information.
There is a question as to the extent that this should be negotiated between the parties or with time just required.
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 understanding the dependency on NSS authentication support and the open question about whether authentication should be negotiated between parties or required after a delay. Done means the web socket protocol uses authentication information and works with NSS checks, with the negotiation behavior decided and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100