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

Certificate verification bypass flag in interactsh-client #618

Closed
ehsandeep opened this issue Jul 31, 2023 Discussed in #616 · 1 comment · Fixed by #620
Closed

Certificate verification bypass flag in interactsh-client #618

ehsandeep opened this issue Jul 31, 2023 Discussed in #616 · 1 comment · Fixed by #620
Labels
Community ✅ Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@ehsandeep
Copy link
Member

Discussed in #616

Originally posted by hahwul July 28, 2023
Hi ProjectDiscovery.
First of all, I'm always grateful for making good tools.

How about adding a flag (e.g. -unsafe-cert) to the interactsh-client for certificate verification bypass? Sometimes, it's challenging to renew the interactsh-server's certificate, and there are situations where using self-signed certificates becomes necessary. Providing this functionality as an optional feature could be helpful. I was thinking of writing the code and submitting a PR, but I wanted to ask for your opinion first.

@ehsandeep ehsandeep added Community ✅ Type: Enhancement Most issues will probably ask for additions or changes. labels Jul 31, 2023
@dogancanbakir dogancanbakir self-assigned this Aug 17, 2023
@dogancanbakir dogancanbakir linked a pull request Aug 17, 2023 that will close this issue
@dogancanbakir dogancanbakir removed their assignment Aug 17, 2023
@dogancanbakir
Copy link
Member

@ehsandeep,
@hahwul is already working on this. Can you assign the issue to @hahwul (I couldn't)?

@hahwul,
Please, let me know if you need any help with the issue.

@Mzack9999 Mzack9999 added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community ✅ Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants