Skip to content
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

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

fujitatomoya
Copy link
Collaborator

closes #4891


.. 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.
Copy link
Collaborator Author

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

Copy link

HTML artifacts: https://github.com/ros2/ros2_documentation/actions/runs/12264223415/artifacts/2302222200.

To view the resulting site:

  1. Click on the above link to download the artifacts archive
  2. Extract it
  3. Open html-artifacts-4900/index.html in your favorite browser

@fujitatomoya fujitatomoya self-assigned this Dec 10, 2024
@fujitatomoya fujitatomoya added the backport-all backport at reviewers discretion; from rolling to all versions label Dec 10, 2024
@fujitatomoya
Copy link
Collaborator Author

@clalancette @ahcorde @Barry-Xu-2018 could you review this?

@fujitatomoya
Copy link
Collaborator Author

@ahcorde thanks for the review.

@fujitatomoya fujitatomoya merged commit 65868a5 into rolling Dec 17, 2024
4 checks passed
@fujitatomoya fujitatomoya deleted the fujitatomoya/using-ros2cli-with-security branch December 17, 2024 17:37
mergify bot pushed a commit that referenced this pull request Dec 17, 2024
Signed-off-by: Tomoya Fujita <[email protected]>
(cherry picked from commit 65868a5)
mergify bot pushed a commit that referenced this pull request Dec 17, 2024
Signed-off-by: Tomoya Fujita <[email protected]>
(cherry picked from commit 65868a5)
fujitatomoya added a commit that referenced this pull request Dec 17, 2024
Signed-off-by: Tomoya Fujita <[email protected]>
(cherry picked from commit 65868a5)

Co-authored-by: Tomoya Fujita <[email protected]>
fujitatomoya added a commit that referenced this pull request Dec 17, 2024
Signed-off-by: Tomoya Fujita <[email protected]>
(cherry picked from commit 65868a5)

Co-authored-by: Tomoya Fujita <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-all backport at reviewers discretion; from rolling to all versions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add explanation how to iterate with secured ROS 2 system via ros2cli
2 participants