Hello COSE key users, (selectively putting the overlapping authors in CC to get their attention -- or should I rather CC CoRE and LAKE?)
implementing more and more of the full CoAP security stack, I find myself creating a lot of private keys, practically stored as CBOR files containing a COSE key. Using a standard format comes with the risk of mixing up key uses, so I'd like to set key_ops on them to ensure that, for example, a P-256 key created for EDHOC method 3 (ECDH) is not used for method 0 (signing). None of the CoAP security standards that use asymmetric keys (EDHOC, Group OSCORE) elaborate on which of their operations relate to which key_ops: Do they match that table? Or would they, in that table, correspond to completely new values for table 5 of RFC9052? Whichever ops they relate to: How do they interact? In particular, outside of the combination of Group OSCORE in group mode (signing) and pairwise mode (static-static derivation), is there any combination that is allowed, which would ease the proof-of-possession step of joining an OSCORE group by performing that proof during EDHOC rather than in a later PoP step? And: How does either outcome follow from the key_ops that should be placed on a key generated for Group OSCORE? Best regards Christian -- You don't become great by trying to be great. You become great by wanting to do something, and then doing it so hard that you become great in the process. -- Marie Curie (as quoted by Randall Munroe)
signature.asc
Description: PGP signature
_______________________________________________ COSE mailing list -- [email protected] To unsubscribe send an email to [email protected]
