Use new sslv3 certificates

[mikaelarguedas]

sslv3 certificates with CA:false extension

WIP: testing ros2/sros2#47

Bionic : Linux

CI on all packages / all platforms:

• Linux
• Linux-aarch64
• macOS
• Windows

connects to ros2/sros2#46

[mikaelarguedas]

Confirmed that this + ros2/sros2#47 fixed secure communication on Bionic for Fast-RTPS. https://ci.ros2.org/job/ci_linux/4318/testReport/test_security.build.test_security/test_secure_publisher_subscriber__Empty__rmw_fastrtps_cpp__secure_comm_0_/test_secure_publisher_subscriber/

Remaining test failures are due to ros2/rclcpp#464

[mikaelarguedas]

This PR update the security artifacts used for testing. They have been generated with the changes from ros2/sros2#47

Relevant changes are:

• Use of Version: 3 in the certificates
• addition of the following extension in the node certificates:

X509v3 extensions:
  X509v3 Basic Constraints: 
    CA:FALSE

• addition of the extension in the generated configuration file ca_conf.cnf

[mjcarroll]

Is there somewhere that describes how to generate these certificates?

[mikaelarguedas]

Is there somewhere that describes how to generate these certificates?

Certificates are generating by using the ros2 security CLI. An introduction of how to use it is available at https://github.com/ros2/sros2/blob/master/README.md.

The artifacts used here for testing are slightly modified by hand as they several of them need to be invalid one way or another.
The permissions files are also slightly different as we allow them to span a wide domain ID range while the ones generated by the tool will be targeting only the host machine's domain ID and reject any other.