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
nat-helper segfaults when running on public server #258
Comments
Making it crash is apparently as simple as sending it two lines of garbage:
Here is the backtrace (I hope it is useful, gdb says something about missing debug symbols):
|
mpiatka
added a commit
that referenced
this issue
Sep 30, 2022
Thanks for reporting. It should now work correctly. |
I confirm the issue is fixed. When a client sends garbage, nat-helper quits the connection. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I compiled nat-helper on Debian Bullseye (amd64) and intend to run it as a service on server with a public IP address. It seems that it crashes after running for a few days. I haven't figured out a way to make it crash on purpose. It could well be that random endpoints connect that don't talk the protocol and send arbitrary messages that make it crash.
I'm not too familiar with cmake. If there is a simple way to create a debug build, please let me know and I'll try to get a backtrace from such a crash.
This is what I get from the service log:
The text was updated successfully, but these errors were encountered: