-
Notifications
You must be signed in to change notification settings - Fork 140
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
Infrequent crash with transparent https #827
Comments
Added more bounds checking to revised get_TLS_SNI and replaced remaining casts on two bytes with two_bytes_to_short call. May be this will also fix renaming issues with BSD port?? See #810 |
i can test with bsd and i will |
it looking good, i did delete unsignedchar flag and i did test , sometimes i get err connection closed and i never seen broke url in access.log |
I'm not sure if the is the same issue as this and #810, but the log truncates the url and puts garbage characters. For example: "2024.10.23 19:36:49","","192.168.1.118","https://update.goog�����","*NETERROR* Failed to negotiate ssl connection to client","","0","0","SSL SITE","1","403","","192.168.1.118","group1","","","-","-","" I'm running Linux Mint 20.2 and e2guardian 5.5.5, installed from deb package, with transparent proxy. This occurs a few times per day. |
Seems to be due to malformed TLS clienthello attack.
The text was updated successfully, but these errors were encountered: