Skip to content
This repository has been archived by the owner on Jul 22, 2021. It is now read-only.

Specify enclaves for ros nodes started by plugins on gzclient #151

Closed
marcoag opened this issue Oct 13, 2020 · 1 comment
Closed

Specify enclaves for ros nodes started by plugins on gzclient #151

marcoag opened this issue Oct 13, 2020 · 1 comment
Labels

Comments

@marcoag
Copy link
Member

marcoag commented Oct 13, 2020

Security on Ros2 requires the user to specify the enclave so it can find the security keys needed for the communication at the DDS level. The usual way to specify this is passing --enclave <enclave_info> as an argument to ros on the command line when executing a ros node, however this doesn't seem to be trivial when ros nodes are created by plugins on gzclient.

Using --ros-args --enclave <enclave_info> seems to work for plugins in gzserver but not for gzclient. It would be good to figure out a way to pass the--enclave to ros when usinggzclient.

It seems that libgazebo_ros_init.so might be in charge of this, so it would be good to digg into the code here to see what code path it's taking:

https://github.com/ros-simulation/gazebo_ros_pkgs/blob/8e3f7d7622fa7422d601010ac34cf4aaf06d4c3c/gazebo_ros/src/gazebo_ros_init.cpp#L140-L146

@marcoag marcoag assigned marcoag and unassigned marcoag Oct 13, 2020
@marcoag marcoag added the SROS2 label Oct 13, 2020
@marcoag marcoag changed the title Secured Ros2 Office: Specify enclaves for ros nodes started by plugins on gzclient Specify enclaves for ros nodes started by plugins on gzclient Oct 13, 2020
@Yadunund
Copy link
Member

Migrate to open-rmf/rmf_demos#55

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants