-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add how to use ros2cli
with security enclaves.
#4900
add how to use ros2cli
with security enclaves.
#4900
Conversation
Signed-off-by: Tomoya Fujita <[email protected]>
|
||
.. note:: | ||
|
||
Avoid using ros2 daemon because it may not have security enclaves, and enough time duration should be given for the discovery in ROS 2 secured network. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
technically we can start the ros2 daemon with security enclaves so that user ros2cli can just call xmlrpc to the daemon to get the discovery information. but I believe that using ros2 daemon would be security breach if user is not careful enough, because it inherits the authentication and permissions from administrator and developers who implicitly starts the ros2 daemon. see more details for ros2/sros2#315
HTML artifacts: https://github.com/ros2/ros2_documentation/actions/runs/12264223415/artifacts/2302222200. To view the resulting site:
|
@clalancette @ahcorde @Barry-Xu-2018 could you review this? |
@ahcorde thanks for the review. |
Signed-off-by: Tomoya Fujita <[email protected]> (cherry picked from commit 65868a5)
Signed-off-by: Tomoya Fujita <[email protected]> (cherry picked from commit 65868a5)
Signed-off-by: Tomoya Fujita <[email protected]> (cherry picked from commit 65868a5) Co-authored-by: Tomoya Fujita <[email protected]>
Signed-off-by: Tomoya Fujita <[email protected]> (cherry picked from commit 65868a5) Co-authored-by: Tomoya Fujita <[email protected]>
closes #4891