tlsv1 alert protocol version... https

[maxiedaniels]

Not sure when things got messed up for me, but suddenly any HTTPS site I try through the tunnel returns 'ssl3_read_bytes:tlsv1 alert protocol version'.

I'm on SSL 1.1.0g. I may have updated it from 1.0.2g recently, but I don't understand why that would have screwed things up.

[jjqq2013]

Thank you for your feedback. Although I have no time to fix this issue now, I propbably know the reason is that this tool is using an ugly implementation to find HTTP transaction from raw stream, maybe tls stream, by chance, and inject auth header, so theoretically it may mistake some tls stream as http activity. The only way to solve this is to reimplement it with more graceful method later. Regards.

2019年3月20日(水) 8:52 maxiedaniels [email protected]:

Not sure when things got messed up for me, but suddenly any HTTPS site I try through the tunnel returns 'ssl3_read_bytes:tlsv1 alert protocol version'.

I'm on SSL 1.1.0g. I may have updated it from 1.0.2g recently, but I don't understand why that would have screwed things up.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sjitech/proxy-login-automator/issues/27, or mute the thread https://github.com/notifications/unsubscribe-auth/AE_djE42S_NIH7FxO-00byIEzilW_v7Hks5vYXhMgaJpZM4b9WKD .