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
A number of protection methods can be applied to a JPEG 2000 codestream to create JPSEC codestreams that are still strictly compliant with JPEG 2000 part 1.
It would be useful if jpylyzer were able to report on the presence of secured codestreams. This could be implemented by checking the presence of one or more SEC markers in the codestream header:
The parameters for these tools are signalled in one or more SEC marker segments located in the
main header of the codestream after the SIZ marker segment. When multiple SEC marker segments are used, they are concatenated and must appear consecutively in the main header. In most cases, all the JPSEC parameters can be signalled in one SEC marker segment. However, in some cases the length of the signalling may exceed the maximum marker segment size. When this occurs, additional SEC marker segments can be used for signalling.
(section 5.5)
The text was updated successfully, but these errors were encountered:
Dev Effort
1D - investigate getting samples
Description
JPEG 2000 Part 8 defines several methods for secured codestreams, including encryption. See:
https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-T.807-200605-I!!PDF-E&type=items
Annex C (interoperability) states:
It would be useful if jpylyzer were able to report on the presence of secured codestreams. This could be implemented by checking the presence of one or more SEC markers in the codestream header:
(section 5.5)
The text was updated successfully, but these errors were encountered: