I am wondering what the goal of making `ros2cli` "security-enabled" is - maybe you can clarify?
If you grant e.g. the `ros2 topic echo` command access to subscribe to a specific topic what make this permission specific to the cli tool? Isn't that conceptionally equivalent of allowing "everyone" to subscribe to that topic. If not, any other entity could simply invoke the command line tool and "get" the information from there since the tool is designed to "output" the requested information.
So I would argue that instead of giving `ros2cli` any kind of explicit permission you could grant the same permission to any entity (which would make the need to identify the command line tool obsolete.
---
[Visit Topic](
https://discourse.ros.org/t/ros2-security-cli-tools/6647/3) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)