Enforce certificates against a CA signer certificate
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- authentication, security
Research direction
The issue does not name any files or tests. Start by locating the existing hostname and certificate verification logic, then determine how peer certificates should be checked against a shared CA authority chain. Done should include an agreed validation behavior and tests covering certificates from the accepted and rejected chains.
Written by the indexing model from the issue text.
Description
Where in the code I can change to enforce the peers certificates against a CA certificate?
My goal is to not only validate the sender host, but if the sender certificate is from the same authority chain of the receiver.
I can try to do it by myself if you tell me in wich part of the code I can change. I think it is at same place you verify the host name of the certificate is from same of the message signer.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from hyperledger-firefly/dataexchange-https
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hyperledger-firefly/dataexchange-https#42 · 2 comments ·
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 20/100
All issues in hyperledger-firefly/dataexchange-https
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#282 ·
-
bug P2 rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area: web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gabe-santana/arkdraw#25 ·
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
codercops/discord-bot#101 · 1 comment ·
Maintainers usually reply within 1 day