Bug 985449 – p11-kit: upgrade to most recent UTF-8 specification

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 985449 - p11-kit: upgrade to most recent UTF-8 specification

Summary:	p11-kit: upgrade to most recent UTF-8 specification

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	p11-kit (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Daiki Ueno
QA Contact:	Hubert Kario
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	983512
	Show dependency tree / graph

Reported:	2013-07-17 10:00 EDT by Florian Weimer
Modified:	2017-08-01 12:52 EDT (History)
CC List:	3 users (show)

See Also:
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 12:52:09 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2017:1981	normal	SHIPPED_LIVE	p11-kit bug fix update	2017-08-01 13:58:17 EDT

Groups: None (edit)

Description Florian Weimer 2013-07-17 10:00:42 EDT

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 12:25:49 EDT

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 05:21:34 EDT

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

Comment 11 errata-xmlrpc 2017-08-01 12:52:09 EDT

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

Note You need to log in before you can comment on or make changes to this bug.