Yes, it's at least strange.
The reproducing configuration is rather complex task, this newer happens in
usual browsing session (and not just in parsing config, of course). I'm
still trying to limit it to something I can publish.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256381,257
may you just try my "fix"? At least, it will save me time for searching in
completely wrong place.
--- nginx-1.7.10/src/http/modules/ngx_http_ssl_module.c.orig 2015-02-10
15:33:34.0 +0100
+++ nginx-1.7.10/src/http/modules/ngx_http_ssl_module.c 2015-03-17
14:55:58.282130993 +0100
@@ -7
> So, the alert is harmless and can be safely ignored.
The real problem - it doesnt, it always accompanied by something like:
nginx[32624] trap invalid opcode ip:47e04d sp:7fff6971ae50 error:0 in
nginx[40+a]
(exactly one "invalid opcode" for each "function you should not call" in
nginx log
and yes, upgrade to libressl 2.1.5 didn't solve this.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256381,257315#msg-257315
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Maxim Dounin Wrote:
---
> If you see problems with nginx 1.7.9, consider following hints
> at http://wiki.nginx.org/Debugging.
I think it will not help (at least if not did by anyone who really knows
both openssl and nginx internals).
the problem
