di-sukharev / di-sukharev/opencommit
Way around work security applications/filters [Feature]:
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.5k
- Forks
- 445
- Avg merge
- 18m
- Merged PRs (30d)
- 2
Description
Description
Hello. I am currently receiving an error when using your package:
self-signed certificate in certificate chain
I have determined that this is due to a security app (zscaler), because when I turn it off, your package works. The problem is, that I need a way to use your package and keep zscaler active. Looking at other online forums, it seems to be a problem for several other packages and various other security measures/apps on work devices. Therefore I believe many of your users will/are impacted by this.
Is there a way to bypass this and still use your package?
Suggested Solution
Update config or package to bypass self-signed certificate error
Alternatives
No response
Additional Context
No response
Contributor 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.
Research direction
Start by reproducing the self-signed certificate in certificate chain error with Zscaler enabled and compare package behavior with it disabled. No file or test entry point is identified in the issue, so locate the package's network configuration first. Done means a supported way to use the package while the security application remains active, with coverage for the certificate scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100