From Newsgroup: alt.privacy
On 12/5/20 12:52 PM, J.O. Aho wrote:
On 05/12/2020 18.05, ShutSentry wrote:
ShutSentry is a virtual dead-man-switch that protects computers from
unauthorized physical access
script stopped working after
killall -9 shutsentry.sh
There are basically two approaches to counteracting the forcible
termination of the script with kill/all.
1) Run the script as another user from the command line, whether that
user be root or another arbitrary user created for this purpose. That
way the normal logged-on non-root user won't have permission to
terminate it. su root -c "shutsentry.sh"
2) A more hackneyed and less optimal solution is to use the feature
within the program "Guard main program process". This will create a
handful of clone processes that monitor the main process for abnormal termination, and trigger an instant shutdown if detected.
When testing the second option, give the program a good 30 seconds or so
after startup before terminating it to generate all the clones. This
approach is of course not as effective as option 1 since if someone is specifically looking for them, the clones could be discovered and
terminated too. But in the event running as another user isn't possible
for some reason, it's better than nothing.
--- Synchronet 3.18b-Win32 NewsLink 1.113