Adding zenoh certificates#329
Closed
ahcorde wants to merge 1 commit into
Closed
Conversation
Signed-off-by: Alejandro Hernández Cordero <ahcorde@gmail.com>
Contributor
Author
|
This is the ca certificate generated with both tools: cert.perm minicapublic/ca.cert.pem```plain Certificate: Data: Version: 3 (0x2) Serial Number: 7e:1e:f8:ec:3b:07:9d:ea:9b:a8:fe:a6:38:79:8b:fe:f5:91:a4:44 Signature Algorithm: ecdsa-with-SHA384 Issuer: CN = sros2CA Validity Not Before: Jan 15 15:33:15 2025 GMT Not After : Jan 14 15:33:15 2035 GMT Subject: CN = sros2CA Subject Public Key Info: Public Key Algorithm: id-ecPublicKey Public-Key: (384 bit) pub: 04:60:46:c7:57:0b:4f:c4:c9:1d:a2:14:bb:dd:86: a2:39:e9:d7:39:9e:b3:07:4d:0a:eb:c6:bc:ca:40: 65:cf:32:f0:20:d9:43:22:b6:56:59:1a:14:46:26: ae:72:ef:66:06:8b:9e:af:88:d3:b7:88:88:a4:62: 7b:0d:e9:79:d8:43:ad:6d:47:df:cf:ec:06:b8:9e: a3:72:63:f3:31:70:a6:fb:96:5c:7a:1c:6d:aa:88: 5d:ab:2f:aa:2c:d0:d6 ASN1 OID: secp384r1 NIST CURVE: P-384 X509v3 extensions: X509v3 Basic Constraints: critical CA:TRUE, pathlen:0 X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Key Usage: critical Digital Signature, Certificate Sign X509v3 Authority Key Identifier: B2:A0:75:8C:CF:B4:99:5F:6F:B9:85:45:E2:0F:43:54:2B:31:D9:FB X509v3 Subject Key Identifier: B2:A0:75:8C:CF:B4:99:5F:6F:B9:85:45:E2:0F:43:54:2B:31:D9:FB Signature Algorithm: ecdsa-with-SHA384 Signature Value: 30:66:02:31:00:93:c1:69:de:e5:ca:67:3d:01:e4:b3:77:b5: 05:fa:fd:ec:42:ff:bd:18:1b:27:8e:ad:bd:45:31:cf:b6:fb: 2a:84:c5:d3:0c:f4:8c:3a:62:4c:51:7b:20:75:d1:f3:db:02: 31:00:94:49:40:72:fc:f1:7c:ec:e8:e4:b5:8c:7a:e0:36:3d: 4f:8b:ab:11:51:af:30:dd:56:ad:a3:82:b4:33:c3:9b:e3:04: 15:49:11:df:ba:90:46:d0:da:de:d6:bc:01:07 ``` |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm playing with zenoh and security in particular with authentication.
The recomended tool to generate certificates in zenoh is minica which is generating certificates with more extensions and with the algorithm
SHA384.This draft PR try to generate using the ros2 common tools the required certificate for zenoh. It's not working I will open this as a draft PR.
Related with ros2/rmw_zenoh#412