-
Notifications
You must be signed in to change notification settings - Fork 17
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
Changing key-management strategies and removing the CBOR encoding #65
Comments
Pre-shared symmetric keys are not supported by the EDHOC specification. X.509 certificates are supported and tested, see the tests. Currently not much of the different combinations of credentials are tested due to a the lack of test vectors. Can you provide a concrete list of the credential types that you want to test. Note that initiator and responded may have different credential type. Generally exchanging the credentials is simple. You need to populate the corresponding |
Thank you for the reply! I used your directions and found the file edhoc_tests_rfc9529.c which uses the x509 certificate. Sadly, when I populated the fields the same way as the function test_edhoc_initiator_x509_x5t_rfc9529 from edhoc_tests_rfc9529.c in the linux_edhoc_oscore sample, I encountered an error: ./build/initiator_client Runtime error: code 1 at src/edhoc/initiator.c:251 Runtime error: code 1 at src/edhoc/initiator.c:299 Runtime error: code 1 at src/main.cpp:217 Is it possible I am not using the test code correctly with the linux_edhoc_oscore sample? And is there a way to get more explicit debug messages? |
Can you describe what you are trying to do? If you want to get a working example running on a linux host probably the the simplest is to build the samples |
I am trying to use X509 certificates without the CBOR encoding. All the examples worked for me but as far as I can see, I can't avoid encoding the certificates. |
Thanks for your feedback. Are you referring to ID_CRED_x? Note that those are COSE header_map by definition. What I can offer is to implement an additional API function that can take a raw ID_CRED_x and a corresponding type and encodes it. This will take some time however. |
I am doing research that involves configuring different key management strategies, such as Pre-shared Keys (PSK), Raw Public Keys (RPK), and dynamically generated keys. I also want to remove the CBOR encoding of the certificates and use an X.509 certificate instead of a C.509 certificate. Is there any built-in support for doing these tasks? If possible, could you please provide me with some guidance on how this can be done? Thank you in advance!
The text was updated successfully, but these errors were encountered: