Re: [Suit] Manifest-07 review

[Russ Housley <[e-mail]>]

I was talking about the file extension for a signed manifest.

Russ


> On Jun 24, 2020, at 10:24 AM, Brendan Moran <[e-mail]> wrote:
> 
> I’m not certain what *we* are talking about. *I* am talking about SUIT_Envelope or, to be more precise, SUIT_Envelope_Tagged (that is #6.TBD(SUIT_Envelope)). I think that SUIT_Envelope_Tagged could have a “.suit” file name extension. I think it’s probably a bad idea to have SUIT_Manifest floating around on your system without the envelope or a signature. Maybe you could add a COSE_Sign to it. Then, you might want a “.cose” file name extension.
> 
> Brendan
> 
>> On 24 Jun 2020, at 14:48, Henk Birkholz <[e-mail] <mailto:[e-mail]>> wrote:
>> 
>> Are we talking about every "software object" that starts with a CBOR tag as defined in this document?
>> 
>> I assume that a manifest in the form of a file can be wrapped or not be wrapped in a SUIT envelope. Would that result in the same file extension ".suit"?
>> 
>> Viele Grüße,
>> 
>> Henk
>> 
>> On 24.06.20 15:42, Brendan Moran wrote:
>>> The intent is to register a CBOR tag that identifies the manifest envelope. This allows detection of manifests by signature in the first 2-3 bytes. A typical filename extension would be fine. I think the most suitable suggestion would be “.suit” if that suits the working group. We’re past the days of 3 letter extensions now, right?
>>> Best Regards,
>>> Brendan
>>>> On 24 Jun 2020, at 14:35, Dick Brooks <[e-mail] <mailto:[e-mail]>> wrote:
>>>> 
>>>> Are there plans for a standard file naming nomenclature to identify software
>>>> objects that contain a suit manifest?
>>>> 
>>>> Today, I use the filename extension to drive an introspection procedure to
>>>> generate an SBOM and having a defined filename extension to indicate that a
>>>> suit manifest is present would help, otherwise I have to parse each file to
>>>> determine which SBOM introspection procedure to invoke.
>>>> 
>>>> Thanks,
>>>> 
>>>> Dick Brooks
>>>> 
>>>> Never trust software, always verify and report! T
>>>> http://www.reliableenergyanalytics.com <http://www.reliableenergyanalytics.com/>
>>>> Email: [e-mail]
>>>> Tel: [phone]
>>>> 
>>>> -----Original Message-----
>>>> From: Suit <[e-mail]> On Behalf Of Waltermire, David A. (Fed)
>>>> Sent: Wednesday, June 24, 2020 9:30 AM
>>>> To: Rønningstad, Øyvind <[e-mail]>; suit
>>>> <[e-mail]>
>>>> Subject: Re: [Suit] Manifest-07 review
>>>> 
>>>> Øyvind,
>>>> 
>>>> Thanks for this review!
>>>> 
>>>> Dave
>>>> 
>>>> -----Original Message-----
>>>> From: Suit <[e-mail]> On Behalf Of Rønningstad, Øyvind
>>>> Sent: Wednesday, June 24, 2020 6:03 AM
>>>> To: suit <[e-mail]>
>>>> Subject: [Suit] Manifest-07 review
>>>> 
>>>> Hi guys, here is a review of manifest-07. Mostly small stuff.
>>>> 
>>>> Questions:
>>>> .... Section 6.4: What are the guidelines for extracting the vendor-id,
>>>> class-id, device-id, or version of a component?
>>>> .... Suit-condition-component-offset is used in an example, but marked as TBD
>>>> in its section. I see that it is described in 6.4 as
>>>> "assert(offsetof(component) == arg)". What are the semantics of "offsetof"?
>>>> .... Can suit-directive-process-dependency be done on a component, or just on
>>>> a dependency? Generally, there seems to be some mismatch between the
>>>> description in 6.4 (which implies that most directives and conditions only
>>>> apply to a component index) and textual descriptions e.g. in 9.8.4.1 and
>>>> 9.8.4.2 (which imply that directives and conditions apply to whichever is
>>>> available of component index and dependency index).
>>>> .... (It would be very beneficial to make 6.4 "Abstract Machine Description"
>>>> more prominent, e.g. by linking from the individual section for commands,
>>>> since 6.4 contains very useful info about how the commands work, and it's
>>>> hard to discover otherwise.) .. What (if any) are the rules regarding when
>>>> to perform dependency-resolution, payload-fetch, and install, and when to
>>>> perform only validate, load, and run?
>>>> .... suit-manifest-sequence-number: "Each Recipient MUST reject any manifest
>>>> that has a sequence number lower than its current sequence number." Are
>>>> there several "current sequence number"s or just one for each SUIT
>>>> processor. Exactly when is the "current sequence number" updated?
>>>> .... What should the processor do when waiting on a suit-directive-wait? Can
>>>> it be interpreted as "try again later", or "busy wait"?
>>>> .... There are important limitations to what sort of commands can be in
>>>> suit-common. Could the limitations be reflected in the CDDL? It seems like a
>>>> natural thing to do, to make the limitations more prominent.
>>>> .... When processing dependencies, how do we know when to a) expect a
>>>> signature and b) check the signature on a dependency manifest?
>>>> .... Did we mean for short payloads to be embeddable in the manifest (I can't
>>>> find this)? This would be very useful for setting configuration options via
>>>> SUIT manifests.
>>>> .... Is the device-identifier unique for each individual device, or for a
>>>> collection of devices?
>>>> .... Why are suit-directive-set-component-index and
>>>> suit-directive-set-dependency-index not implemented through set-parameters?
>>>> Are they subject to the same override mechanics? If not, it might be
>>>> confusing with suit-parameter-source-component, which seems to be analogous
>>>> to set-component-index, but might have subtly different behavior because of
>>>> override mechanics.
>>>> 
>>>> Nits:
>>>> .... Suit-directive-fetch: "manifest-index" is not referred to elsewhere in
>>>> the document.
>>>> .... Section 7: Suggested edit in bold: "A digest should always be set using
>>>> Override Parameters, since this prevents a less-privileged dependent OR
>>>> dependency from replacing the digest."
>>>> .... suit-condition-update-authorized seems like it could use some metadata
>>>> to help determine what is being authorized, e.g. A human readable prompt if
>>>> user interaction is required, or an identifier if multiple instances of the
>>>> condition are used in a manifest.
>>>> 
>>>> 
>>>> Thanks for the good work,
>>>> 
>>>> Øyvind
>>>> 
>>>> _______________________________________________
>>>> Suit mailing list
>>>> [e-mail]
>>>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.o
>>>> rg%2Fmailman%2Flistinfo%2Fsuit&amp;data=02%7C01%7Cdavid.waltermire%40nist..go
>>>> v%7C909e99a025494e915e6008d81825e30f%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%
>>>> 7C0%7C637285898291416907&amp;sdata=Hww6iMALkbaHZQLb1VeYGCDfb7yrQGbpUbUa%2FD5
>>>> u4Fo%3D&amp;reserved=0
>>>> 
>>>> _______________________________________________
>>>> Suit mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/suit
>>>> 
>>>> _______________________________________________
>>>> Suit mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/suit
>>> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
>>> _______________________________________________
>>> Suit mailing list
>>> [e-mail] <mailto:[e-mail]>
>>> https://www.ietf.org/mailman/listinfo/suit
> 
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> _______________________________________________
> Suit mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/suit