Decide if/how to handle SSL cert authenticity warning for repo connection
Open
Nobody has claimed this yet.
security
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
We can suppress this warning here, but I don't want to until we understand it.
2022-05-25 13:53:08.095 GMT13:53:08.087 [warning] Description: 'Authenticity is not established by certificate path validation'
2022-05-25 13:53:08.095 GMT Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
@stuartc , you were keen to see the warning ⬆️
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 reading config/runtime.exs at lines 40-41 and the reported SSL warning. Investigate how the repo connection is configured and determine whether certificate authenticity should be handled or the warning suppressed. Done means the project has a decided, documented approach and the configuration reflects that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100