Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add --no-check-certificate as a config option #135

Closed
furi0us333 opened this issue Oct 26, 2021 · 0 comments · Fixed by #139
Closed

Add --no-check-certificate as a config option #135

furi0us333 opened this issue Oct 26, 2021 · 0 comments · Fixed by #139
Labels
enhancement New feature or request

Comments

@furi0us333
Copy link
Contributor

Is your feature request related to a problem? Please describe.
When a user is required to use the --no-check-certificate option, they must include it for all subcommands. This makes the workflow a bit clunky for that use case.

Describe the solution you'd like
Have the --no-check-certificate option as a configuration parameter option stored in the settings.yaml file. When set, this would run all commands with that option set. This will allow the user to omit that option from the command line. NOTE: We should clearly warn the user that they are running in this mode for each request. Maybe a red warning text after each request?

Describe alternatives you've considered
The current command option works, but is not as clean.

Additional context
This is impacting customers with SSL decryption and other MITM solutions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant