Uploaded image for project: 'Service Design and Creation'
  1. Service Design and Creation
  2. SDC-3489

Signature of the NSD signed package should have the extension .cms, not .sig.cms

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • Honolulu Release
    • Honolulu Release
    • SDC
    • None

      In the ETSI 3.3.1 SOL007 Option 2 of package security, the signature of the NSD signed package should have the extension .cms, not .sig.cms.

      Currently that is the structure of the package: 

      package.zip
      --package.sig.cms
      --package.cert
      --package.csar
      

       The .sig.cms is only for internal artifacts of the package.csar. But for the csar signature itself, should have the same base name as the CSAR with the .cms extension.

      From the ETSI 3.3.1 SOL007, section 5.2:

      The signature file shall have an extension .cms and the same name as the CSAR file.

       Introduced in SDC-2614.

            andre.schmid andre.schmid
            andre.schmid andre.schmid
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: