You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In section 3.3. of the secure content specification the test states "OPC parts that are encrypted MUST be associated with the package root through a Encrypted File relationship, and each SHOULD have an entry in the Key Store. If a custom OPC part is not referenced by a Encrypted File relationship it is assumed they are not encrypted and MUST NOT be any entry in the Key store associated to the file."
The phrase "associated with the package root" led me to believe that the encryption relationship should be in the root .rels. The example encryption relationship XML in the spec does not look like a root .rels definition, so I suspect that the correct location is in the .rels file associated with where the encrypted content is referenced and not the root .rels
This needs clarification in the specification.
The text was updated successfully, but these errors were encountered:
In section 3.3. of the secure content specification the test states "OPC parts that are encrypted MUST be associated with the package root through a Encrypted File relationship, and each SHOULD have an entry in the Key Store. If a custom OPC part is not referenced by a Encrypted File relationship it is assumed they are not encrypted and MUST NOT be any entry in the Key store associated to the file."
The phrase "associated with the package root" led me to believe that the encryption relationship should be in the root .rels. The example encryption relationship XML in the spec does not look like a root .rels definition, so I suspect that the correct location is in the .rels file associated with where the encrypted content is referenced and not the root .rels
This needs clarification in the specification.
The text was updated successfully, but these errors were encountered: