Bug 985449

Summary:	p11-kit: upgrade to most recent UTF-8 specification
Product:	Red Hat Enterprise Linux 7	Reporter:	Florian Weimer <fweimer>
Component:	p11-kit	Assignee:	Daiki Ueno <dueno>
Status:	CLOSED ERRATA	QA Contact:	Hubert Kario <hkario>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	dueno, hkario, nmavrogi
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	p11-kit-0.23.5-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 16:52:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	983512

Description Florian Weimer 2013-07-17 14:00:42 UTC

common/utf8.c:utf8_to_uchar() does not reject surrogate characters in the input, which are invalid in UTF-8.  UTF-8 was redefined in RFC 3629 so that code points in astral planes (unreachable with UTF-16) are no longer valid UTF-8.

The other conversion routines in that file do not seem to handle surrogate characters properly, either.

I'm not sure how relevant this is in practice, and if you can use platform conversion routines like iconv instead of rolling your own thing.

Comment 2 Stef Walter 2013-07-17 16:25:49 UTC

Agree with this. But punting to future release. The UTF-8 support is only used to generate OpenSSL symlinks when extracting. So not totally critical. Need to make sure that what we do here is compatible with how OpenSSL does this stuff.

Comment 6 Daiki Ueno 2016-09-23 09:21:34 UTC

https://github.com/ueno/p11-kit/commit/900658d6677b3973756816e8a93a53f87e89e2c5

Comment 11 errata-xmlrpc 2017-08-01 16:52:09 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1981