-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Nginx/openssl version compatibility for releases #27
Comments
0.4.1 was successfully tested aginst (and it works in prod pretty good):
+1 |
OpenSSL_1_1_1-stable ==55768==ERROR: LeakSanitizer: detected memory leaks Indirect leak of 16384 byte(s) in 1 object(s) allocated from: Indirect leak of 16384 byte(s) in 1 object(s) allocated from: Indirect leak of 16384 byte(s) in 1 object(s) allocated from: Indirect leak of 16384 byte(s) in 1 object(s) allocated from: Indirect leak of 16384 byte(s) in 1 object(s) allocated from: Indirect leak of 6400 byte(s) in 1 object(s) allocated from: Indirect leak of 5349 byte(s) in 1 object(s) allocated from: Indirect leak of 4544 byte(s) in 1 object(s) allocated from: Indirect leak of 4280 byte(s) in 1 object(s) allocated from: Indirect leak of 4280 byte(s) in 1 object(s) allocated from: Indirect leak of 4280 byte(s) in 1 object(s) allocated from: Indirect leak of 4096 byte(s) in 1 object(s) allocated from: Indirect leak of 4096 byte(s) in 1 object(s) allocated from: SUMMARY: AddressSanitizer: 119245 byte(s) leaked in 13 allocation(s). nginx -t Since then, memory-related issues continue to occur. Is there a compatible version out there? |
nginx.patch should be ok for all 1.2x relase, and I added a openssl 3.2 patch in https://github.com/phuslu/nginx-ssl-fingerprint/blob/master/patches/openssl.3_2.patch |
Stumbled on this while doing testing, was pulling
master
while testing a nginx 1.21.4 / openssl 1.1.1q deployment and was getting segfaults. Traced this to the 0.4.0 and subsequent patches, reverting to 0.3.0 tag worked fine. Would be nice to understand what version compatibility there is for the releases.The text was updated successfully, but these errors were encountered: