Open psytester opened 5 years ago
This is actually already planned. So no need to convince me in any way. :)
However, please be prepared that some selected services will still need root access due to requirements to provide global executable rights. But as said, some changes are already planned in that areas. Just be prepared that this might take some time.
The todays (O)CCU concept is a genuine offer to be "hacker friendly", because all processes are running in root user context. Any "possible" vulnerability leads to fully unreserved exploitable access.
As you stated that RaspberryMatic is something like a eQ-3 pre-Beta / Proof Of Concept / input channel for official eQ-3 releases, please introduce a state of the art user and service daemon managment with non privileged users. Starting with lighttpd to use the build in but not activated settings, because the CCU does not have such account:
Or use the "www-data" account.
Next is the ReGaHss itself as non root! The Java process for HMIPServer.jar, too and last but not least the processes /bin/eq3configd , /bin/rfd and /bin/eq3-uds-services / ....
AND adjust the file system permissions according to its needs. Today all directories and files are owned by root, readable by root user, by group "root" and by others
Limiting the (read) access to users and goups and change the ownership of sensitive spot files. Why do I need to be able to read the
homematic.regadom
as any other process or user?