Joshua Rogers

I've fixed the Shellcheck warnings, and fixed three calls to `kill -SIGTERM` as well. There was already one `kill -TERM`, fyi.

Also, today I realized there is a more elegant solution to solving this bug than creating the (local) whole function for it. This patch provides the same functionality: ``` ---...

That should do it. Please test.

Great! With this patch and all of the others applied, Wifibox now works 100% on my system. Feel free to add it to the supported list. CPU: Core i7-4870HQ CPU...

>I'd say it's more of a design choice overall at present: report on something bound to existing directives, rather than report on things completely missing. After second thought, I agree....

@prestonprice57 not surprising:) fyi, following the instructions of your tool to install it with `pipx`, then using `export OPENAI_API_KEY=...` then: ``` $ fraim run code --location https://github.com/megamansec/ssh-snake --model=openai/gpt-4 2025-10-09 16:49:33,991...

this is doomed to fail in various ways. e.g. ``` if ($http_origin !~ ^https://yandex[0-9]\.com$) { } ``` could be either a legitimate or vulnerable expression. hmm.

The remaining recommendation "_Ideally, I think we'd have some kind of tty_drain_freed -> destroy_dev_drain_pending -> taskqueue_drain_" is not done yet: I have not had time yet to try this.

Unfortunately, I never got time to make the changes requested ("without the timeout by adding some plumbing through the tty layer to drain the deferred destroy_dev taskqueue"). Perhaps a freebsd...

Note: doesn't pick up the configuration: ``` map $http_origin $allow_origin { ~^https://(.*\.)?example.com$ $http_origin; default ""; } add_header Access-Control-Allow-Origin $allow_origin always; ``` We can do that once #58 lands.