-
Avery Pennarun authored
There were still a few conditions under some OSes that would cause firewall.py to terminate without cleaning up the firewall settings. 'pkill sshuttle' was one of them. Ignore a couple more signals to further ensure a correct cleanup. (This only affects sshuttle --firewall, which is a subprocess of the main sshuttle process. The firewall is supposed to exit automatically whenever the client exits, and so far that part seems to work reliably.)
e5251969
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| compat | ||
| ui-macos | ||
| Makefile | ||
| all.do | ||
| assembler.py | ||
| clean.do | ||
| client.py | ||
| default.8.do | ||
| do | ||
| firewall.py | ||
| helpers.py | ||
| hostwatch.py | ||
| main.py | ||
| options.py | ||
| server.py | ||
| ssh.py | ||
| sshuttle | ||
| sshuttle.md | ||
| ssnet.py | ||
| ssyslog.py | ||
| stresstest.py |