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

Fix handling of OctetString in get_options() function #5558

Closed
wants to merge 1 commit into from
Closed

Fix handling of OctetString in get_options() function #5558

wants to merge 1 commit into from

Conversation

Nikitosh
Copy link

@Nikitosh Nikitosh commented Apr 5, 2019

The OctetString option was handled as if they have IPP_TAG_NAME tag, though it stores its data in unknown.data instead of string.text and also stores length instead of '\0' end symbol.

@michaelrsweet
Copy link
Collaborator

This fix is incomplete - ipp_length() also needs to be updated...

michaelrsweet added a commit that referenced this pull request Apr 15, 2019
scheduler/job.c:
- get_options(): Correctly encode IPP_TAG_STRING as a quoted string or a hex
  string depending on the value.
- ipp_length(): Handle IPP_TAG_STRING separately.
michaelrsweet added a commit that referenced this pull request Apr 15, 2019
scheduler/job.c:
- get_options(): Handle IPP_TAG_STRING separately and either provide a quoted
  string or a hex string, depending on the value.
- ipp_length(): Handle IPP_TAG_STRING separately.
@michaelrsweet
Copy link
Collaborator

I'm also opting to support hex encoding when the string contains binary data.

[master 5483fd2] Correctly encode octetString values for print filters (Issue #5558)

[branch-2.2 803b6de] Correctly encode octetString values for print filters (Issue #5558)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants