Kai Kretschmann

Addition: It seems the conditions like [PATH=/abc/] always get true even if it doesn't make sense.

It even happens when I explicitly uses a non root user in docker: https://gitlab.kretschmann.software/kai/commonapisample/-/jobs/7121 The processes see their ID 1000 which is right, but the vsomeip reports funny numbers.

It seems related to GCC in version 11, if reduce the docker root package to gcc:9.3.0 that error is gone. So there must be some problem in the GCC 11...

I didn't have yet the time to continue on it. But I think it should be handled/solved as this might be a security risk otherwise. Hoping to have a look...

I just checked tht again and still have that problem. By just changing the container from Ubuntu 20.04 to 21.10 (which updates gcc from 9 to 11) and recompiling everything...

I'm using the ubuntu given ones 1.74 by installing libboost-all-dev within the container. I also cloned the vsomeip to my server and changed/added some debugging to it. The boud_uid didn't...

At least for local communication one should be able to trust those IDs. And if I get randomly a "0" then it looks like beeing root without haven those rights...

At least the latest package.json dependency changes would be nice to have as a new 4.3.1 patch level version.

same here, I'm puzzled.

As alternative an authentication header in the outgoing request might help too. With this static auth I could trigger stuff to gitlab for example.