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
I don't know whether this still applies to modern Node, but for obscure reasons I'm using 6.11, and winston-syslog when using TCP needs a process.on('exit', ...) handler (I think in connect()) that performs ...
... otherwise the server side doesn't tear down its side of the TCP connection, and the number of "established" connections showing from the client side increases until such point as the syslog service (or the kernel or something) blocks that client. Effectively, you can DoS yourself if you have lots of short-running Node apps that do syslog over TCP.
The text was updated successfully, but these errors were encountered:
I don't know whether this still applies to modern Node, but for obscure reasons I'm using 6.11, and winston-syslog when using TCP needs a
process.on('exit', ...)
handler (I think inconnect()
) that performs ...... otherwise the server side doesn't tear down its side of the TCP connection, and the number of "established" connections showing from the client side increases until such point as the syslog service (or the kernel or something) blocks that client. Effectively, you can DoS yourself if you have lots of short-running Node apps that do syslog over TCP.
The text was updated successfully, but these errors were encountered: