SIG Security Meeting : Nov 5th
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 6
- Forks
- 3
- Avg merge
- 1h 54m
- Merged PRs (30d)
- 1
Description
Attendees: Phil (42Crunch ) / Peter Davis (Chief Architect / AirsideMobile)
Discussion :
- From Jeremy’s proposal, specifying where the token must be is a great idea
We must enrich the proposal so that : - What the token is about (client, Resource Owner, exchanged data, operation invocation context -like HTTP-Signature, etc…)
- Which information the token should contain
- Where to obtain a token
can be described
- How to describe Certificate pinning
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
The issue contains meeting notes about enriching a token proposal and describing certificate pinning, but names no files, tests, or implementation entry points. Start by locating the referenced proposal and deciding the intended scope; the work is done when the agreed security requirements are documented in the project’s specification.
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
- 25/100