ros2 / sros2

tools to generate and distribute keys for SROS 2
Apache License 2.0
89 stars 44 forks source link

Add in some documentation about how to use CRLs on Linux. #272

Closed clalancette closed 2 years ago

clalancette commented 3 years ago

Signed-off-by: Chris Lalancette clalancette@openrobotics.org

codecov[bot] commented 3 years ago

Codecov Report

Merging #272 (4112553) into master (e5e90f0) will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #272   +/-   ##
=======================================
  Coverage   77.25%   77.25%           
=======================================
  Files          25       25           
  Lines         664      664           
  Branches       55       55           
=======================================
  Hits          513      513           
  Misses        131      131           
  Partials       20       20           
Flag Coverage Δ
unittests 77.25% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...s_ws/src/dx4ckyvxe5k/sros2/sros2/sros2/__init__.py
...xe5k/sros2/sros2/sros2/policy/defaults/__init__.py
...x4ckyvxe5k/sros2/sros2/sros2/keystore/_keystore.py
ros_ws/src/dx4ckyvxe5k/sros2/sros2/sros2/errors.py
ros_ws/src/dx4ckyvxe5k/sros2/sros2/setup.py
...yvxe5k/sros2/sros2/sros2/verb/create_permission.py
...ws/src/dx4ckyvxe5k/sros2/sros2/sros2/_utilities.py
...ckyvxe5k/sros2/sros2/sros2/verb/create_keystore.py
...4ckyvxe5k/sros2/sros2/sros2/verb/create_enclave.py
...e5k/sros2/sros2/sros2/policy/templates/__init__.py
... and 40 more

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update e5e90f0...4112553. Read the comment docs.

clalancette commented 3 years ago

Friendly ping on this; I'd like to get some documentation about this feature landed. Thanks!

clalancette commented 2 years ago

Going ahead and merging with one review; since it is a documentation-only change, it should be safe enough. Also not running CI and relying on the PR checks for the same reason.