And, for your amusement. I recently found this homemade cable splitter hidden away in the ceiling which would explain my WAN issues.
WOW! There are some real "geniuses" in this world!!!
I'm surprised the cable company didn't catch that, as they do a lot of work to ensure the integrity of their system, as they are required by law, to prevent interference to other services.
Minicom = my common app to use as well :) Thanks for the help so far everyone! At some point I'll get this connection worked out. Or, I'll finally decide that the FW-7551 is actually and totally dead on the output tip.
Using the acme package might be a solution. I haven't tried that.
That link helped to get me started. Using the correct search terms massively helps getting more relevant search results. Thanks a lot for the quick response and the nudge in the right direction.
I dug around some old mailing lists. The warning pertains to cases where a person has a normal account on the host, and root access in a jail. He can then suid a binary, eg. vi, and use that suid executable on the host.
If you where to have this edge case, the problem is easy to fix, just chmod 0700 your jail dir on the host.
SHM was also mentionen but as I stated, it's disabled by default.
Yes, you should update to 2.4.4p2 when you can. Be aware that is quite a significant upgrade however:
https://www.netgate.com/blog/pfsense-2-4-4-release-now-available.html
You would expect code in HEAD to be in the next release. That page was last updated in August though.
FreeBSD 11.2 that pfSense 2.4.4 is built on includes those patches:
https://www.freebsd.org/security/advisories/FreeBSD-SA-18:03.speculative_execution.asc