[cups.bugs] [HIGH] STR #2593: UTF-8 changes consitutes an API change

twaugh.redhat twaugh at redhat.com
Tue Nov 13 09:27:39 PST 2007


DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

In 1.3.4, requests in encodings other than ASCII and UTF-8 are now
rejected.  In general I think this may be the right direction, however
there is a consequence of this that you may not have intented: the API is
now changed.

Several CUPS API functions now no longer give responses in the user's own
locale encoding but in UTF-8.  In other words, rejecting requests in other
encodings is *not* sufficient to protect unwary client applications from
this change.

This is an API change which should at the very least be deferred until
1.4.x.

To give one particular example, cupsGetJobs2() may now return a job-name
attribute encoded in UTF-8 whereas previously it would have been in the
'native' encoding.  This will cause a client application running in a
non-UTF-8 encoding locale to display incorrect characters.

(The fact that this change was introduced in the same release as a major
security fix is nothing short of astounding.)

Link: http://www.cups.org/str.php?L2593
Version: 1.3.4





More information about the cups-devel mailing list