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

proxify does not support SSL 1.0 #303

Closed
matheusvsl opened this issue Jun 8, 2023 · 0 comments · Fixed by #377
Closed

proxify does not support SSL 1.0 #303

matheusvsl opened this issue Jun 8, 2023 · 0 comments · Fixed by #377
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.

Comments

@matheusvsl
Copy link

I'm trying to use proxy with the old TLS 1.0 protocol, but seems that it does not support this version. I understand that proxify could be used to offer an easy solution as upstream proxy to environments that also does not support this protocol (such as burp)

Proxify version:

v0.0.9

Current Behavior:

When I try to access a website behind TLS 1.0 I receive the following message:

2023/06/08 10:18:47 [041] WARN: Cannot read TLS response from mitm'd server tls: server selected unsupported protocol version 301

Expected Behavior:

proxify should proxy this website normally

Steps To Reproduce:

Configure your browser to work with proxify and try to open a website using TLS 1.0.

@matheusvsl matheusvsl added the Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. label Jun 8, 2023
@RamanaReddy0M RamanaReddy0M linked a pull request Sep 21, 2023 that will close this issue
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Sep 21, 2023
@ehsandeep ehsandeep added this to the proxify v1.0.0 milestone Sep 21, 2023
@ehsandeep ehsandeep removed this from the proxify v1.0.0 milestone Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Completed Nothing further to be done with this issue. Awaiting to be closed. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants