Simon Hoinkis

> @mossmaurice Do we still need the markdown linter? We concluded that we can postpone this since we also postponed the release. @zmostafa Yes, the markdown linter would be much...

@YeahhhhLi Thanks for opening this issue. Did you have a look at the [access control example](https://iceoryx.io/v2.0.2/examples/ice_access_control/)? There, the setup regarding users and groups is described in detail. Unfortunately, user/groups configuration...

@YeahhhhLi > we hope that we can meet our needs by modifying the .toml file. Turns out I was mistaken. It should be possible to configure the groups with a...

@YeahhhhLi Thanks for the detailed post! Which version of iceoryx are you using? > just tried to associate the user and user group, and then restarted, and found that some...

@JMueIIer @marthtz Will you continue to work on this topic? Will it be available for iceoryx 2.0 (~December 2021)? cc @CarolinaGGB

@qclzdh @elBoberido I've not come to a final conclusion, but my feeling is the custom user header could also be helpful for `rmw_iceoryx`, see here: https://github.com/ros2/rmw_iceoryx/pull/84

@ymarcov Thanks for creating this issue! 1. I agree with what was said above. 2. I understand the issue and that it can easily lead to misuse. However, my point...

> @elfenpiff We weren't aware of the issue until @ymarcov discovered it and I would bet it would also slip future PR. > > @elBoberido well, I was aware* that...

@elBoberido The workaround is ok for me long term. However, we should document this somewhere not to forget if e.g. new files are added. I suppose the `CONTRIBUTING.md` would be...

@elfenpiff > universally inject packages on a specific service You mean something like an `icepipe` example? :smirk: