In information security, integrity means that data cannot be modified undetectably.
This answer raised my interest, of course, I want to guarantee the integrity of my OS, outlined here. Suppose a security camera project where you store every photo to a folder. I used fswebcam -program, crontab and some bash scripts to automatically to shoot photos. I did it for second-hand store on very low budget, re-used old laptops and old cameras, and with limitations such as no internet connection. I am unsure whether the os, obsd, offers some extra features not in use which I could use, perhaps some sort of paranoia mode. Basically, each comp had clearly predefined schedule: take a photo (execute a script, ...), save it to a file, ... -- if anything different, alarm. I don't know whether there is any way to freeze the rest of the os in a way that it is totally unusable in other services. Some of the laptops could be shooters while one laptop could be a receiver or core data center.
- How can you do it with obsd laptops that can work in concert?
- How could you guarantee the integrity of the OS so that no picture cannot be removed or if removed it will leave traces?
- In which mode would you put a shooter and a receiver obsds? Are they in different modes and why?
Related but not the same