Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add detection of secured codestreams #94

Open
bitsgalore opened this issue Oct 26, 2016 · 3 comments
Open

Add detection of secured codestreams #94

bitsgalore opened this issue Oct 26, 2016 · 3 comments
Assignees
Labels
feature New functionality to be developed P2 Medium priority issues to be scheduled in a future release

Comments

@bitsgalore
Copy link
Member

bitsgalore commented Oct 26, 2016

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:

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)

@bitsgalore bitsgalore self-assigned this Oct 26, 2016
@boxerab
Copy link

boxerab commented Feb 17, 2017

Interesting. Do such files exist out in the wild, and if so, who is using this feature? Just curious.

@bitsgalore
Copy link
Member Author

I've no idea, a colleague alerted me to the existence of this feature. I've never come across any files that are using this BTW.

@boxerab
Copy link

boxerab commented Feb 17, 2017

Thanks. For testing, I suppose you would need at least one.

@ghost ghost added feature New functionality to be developed P2 Medium priority issues to be scheduled in a future release labels Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality to be developed P2 Medium priority issues to be scheduled in a future release
Projects
None yet
Development

No branches or pull requests

2 participants