You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 22, 2023. It is now read-only.
PID 20 received SIGSEGV for address: 0x11
/srv/app/node_modules/segfault-handler/build/Release/segfault-handler.node(+0x1185)[0x7fc0d1619185]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fc0d1dfe340]
/usr/local/bin/node(uv_write+0x1c)[0xb8a84c]
/usr/local/bin/node(_ZN4node12TLSCallbacks6EncOutEv+0x23a)[0xb621ea]
/usr/local/bin/node(_ZN4node12TLSCallbacks21OnClientHelloParseEndEPv+0x30)[0xb64340]
/usr/local/bin/node(_ZN4node6crypto7SSLWrapINS_12TLSCallbacksEE9EndParserERKN2v820FunctionCallbackInfoINS4_5ValueEEE+0x5d)[0xb49b1d]
/usr/local/bin/node(_ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE+0x92)[0x781002]
/usr/local/bin/node[0x79e5f8]
[0x1fb117c0634e]
If i'm reading this correctly, a client isn't sending proper TLS request and causes an internal node failure.
I'm determined to find the root cause of this. If this is genuinely not my fault (dproxy project), then other projects using TLS and SNI may be endangered.
Running https://github.com/CastawayLabs/dproxy.js.. Occasionally, it quits with segmentation fault..
It is caught using
segfault-handler.Stack trace:
If i'm reading this correctly, a client isn't sending proper TLS request and causes an internal node failure.
I'm determined to find the root cause of this. If this is genuinely not my fault (dproxy project), then other projects using TLS and SNI may be endangered.
Happened for v0.11.13 and v.0.11.14
/cc @tjfontaine as it seems related to TLS