This is a reply to @ben-grande regarding this comment:
[…] there are many things to consider:
- it is a shellscript, Qubes OS prefers python
More things to consider:
- prefers != mandates (IIUC)
- it is a work in progress thing. I will post a new version when ready. I am months late with so many things due to serious health issues but at least I am alive.
- While I have a (rusty) C/Assembly/others background, I still don’t “speak” Python. Shame on me.
- for the particular task, I don’t quite see the benefits of Python (and I admit the reason may be my lack of expertise)
- shell script is in every distro, out of the box, even minimal. The same largely applies to Python, especially considering Qubes OS. However, if some day in the distant future Python becomes no longer so preferred, or if dom0 finally gets proper minimisation, it may turn out that the bash version is more suitable (just a speculation)
- it uses a blocklist, adding a new log file to the system would be a cat and mouse game, the proper way would not save those files in non tpmfs in the first place
What do you call a “blocklist”?
- there are no unit or integration tests
Because it was never planned to become an integral part of the system. If there is such plan, that might become an actual (sub)project with proper design and structure.
- a live system would be much better to guarantee that nothing is ever written to disk
Unless I am missing something, the only thing that is written to persistent storage are the logs. Qubes OS is simply not designed to guarantee any non-logging, so if there is any expectation for the opposite, it must be addressed at the OS level, not at the level of a component.
I welcome any further comments which may improve this micro project.
Thank you for your feedback!