Hi Ben,
On Mon, May 01, 2023 at 10:41:32PM -0700, Benjamin Kaduk wrote:
> > * Does pinned-domain-pubk work also for COSE keys as used for signed
> > CWTs? (If so, is there a key identifier to go with it?)
>
> COSE key identifiers ('kid') are not exactly what you would typically call
> a "key identifier" in unconstrained spaces. In particular, they are just
> for optimizing lookup over trial decryption, and you have to associate your
> authorization data with the full key entry, not with the 'kid'. COSE 'kid'
> are not globally unique, and you might run into a lot of places using kid
> of '0' and relying on context to infer which one is meant.Yes, that's the way I'd hope they could be used. For example, if a device were onboarded into an ACE domain with three AS that's using the ACE-OSCORE profile with the devices, they'd obtain three symmetric keys with a key identifier h'00', h'01' and h'02' respectively, so that when the device receives a token, it'll try the one key and not any. > It makes me nervous, but just because of the normal shared-key threat > model. That'd make me nervous too, but see above -- with shared keys, it'd be at least my expectation that there's a key for every AS. ... which also means that there'd be a need to update data that originally came in on an ANIMA voucher, and I don't know whether that's better done through ANIMA again or through ACE. > > * Once onboarding onto ACE has completed, all the device's identity > > would be ACE (except for the IDevID that's left in place for a factory > > reset). Is that fine with an ANIMA setup? > > Without the full context of the preceding thread, it's hard to be sure I > understand properly, but I think yes, ANIMA expects LDevID for onboarded > devices, so if you're building ACP using ACE crypto it should be fine. I'm not sure the thread context will help, but I can rephrase the question now (assuming it's using ACE-OSCORE for simplicity): The identity a device (after onboarding onto an AS through ANIMA means) will have as its operational identity the (AS-URI, audience) tuple, confirmed by the shared key(s) it has obtained. It would not receive any certificate, and not use the IDevID unless onboarding is started anew. Is that identity now an LDevID (even though it has a completely different shape than the IDevID), or is a certificate based LDevID still created as part of the process, or can the device happily complete the ANIMA processes without an LDevID? Thanks Christian -- To use raw power is to make yourself infinitely vulnerable to greater powers. -- Bene Gesserit axiom
signature.asc
Description: PGP signature
_______________________________________________ Ace mailing list Ace@ietf.org https://www.ietf.org/mailman/listinfo/ace
