This is a curiosity question, not a bug, and I'm running fine now. Had an instance where I got a message that permissions were not set correctly on BOINC Lockfile in one of the slots. Went and took a look and the file was owned by system, not BOINC Project. As I thought BOINC on the Mac ran setuid I'm wondering where it came up with system for ownership?

As a bit of background, the poor machine had crashed, but was still operating enough that I SSH'd into it to reboot it, expecting that to shut BOINC down somewhat gracefully. Don't like that power button as it leaves too much hanging. Watched the processes die off, top, BOINC was long dead but there was a Seti@Home thread still consuming CPU even after the finder was dead!

Just wondering if because that process was orphaned, if when Init claimed ownership of the orphan process if that might have been where the owner of the lockfile changed hands. If so that might be an open security hole in the O/S which might be exploitable to elevate privilege.

Thoughts?

---