| commit | a06626d1ad963f6998237a332eab9ac9392b7c7a | [log] [tgz] |
|---|---|---|
| author | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Thu Nov 24 15:22:40 2022 +0000 |
| committer | Krzysztof Grobelny <krzysztof.grobelny@intel.com> | Mon Jan 23 10:54:37 2023 +0000 |
| tree | b640aad4acbc93e2060758d7b3fbb1915d874582 | |
| parent | 0452976942f7c9e9a3ace74bf71b946d53ead203 [diff] |
Added security checks for symlinks Added security checks which prevents service from interacting with symlinks. It is not possible to list/delete/read/write to symlinks. Tested: Added unit tests which confirm that: - Symlinks cannot be removed - Symlinks are not listed - Symlinks cannot be overwritten - Symlinks cannot be read Signed-off-by: Krzysztof Grobelny <krzysztof.grobelny@intel.com> Change-Id: I50d6d10dac81fd454e7e30520a7c47d5146be58c
This component implements middleware for sensors and metrics aggregation.
This application is implementation of Telemetry proposed in OpenBMC design docs [1].
It's responsible for:
[2],[3] updates.[4]There are two way to build telemetry service:
To build it using bitbake follow the guide from OpenBMC docs[5]. To build it using meson follow the quick guide to install meson[6] and then run below commands
meson build
cd build
ninja
After successful build you should be able to run telemetry binary or start unit tests
./tests/telemetry-ut ./telemetry
In case if system is missing boost dependency, it is possible to build it locally and set BOOST_ROOT environment variable to location of built files for meson. After this change meson should be able to detect boost dependency. See [7] for more details.
More information can be found in OpenBMC docs repository [8].