Bug 1138339

Summary:	Apple iOS7 "trust" bug on libimobiledevice 1.1.5
Product:	Red Hat Enterprise Linux 7	Reporter:	Alexandros Gkesos <agkesos>
Component:	libimobiledevice	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	cww, jkoten, mclasen, ppostler, tpelka
Target Milestone:	rc	Keywords:	OtherQA, Rebase
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 21:28:28 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:	1297830, 1298243, 1313485, 1393395

Description Alexandros Gkesos 2014-09-04 14:23:52 UTC

Description of problem:
The current version of the library presents the "trust bug" where Apple devices with iOS 7 will not pair with the host and keep prompting the user to "Trust this computer". 

Version-Release number of selected component (if applicable): 
libimobiledevice-1.1.5-6.el7.x86_64 

How reproducible: Everytime


Steps to Reproduce:
1. Connect Apple device upgraded to iOS7 to a usb port


Additional info:
Similar request on Fedora Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1073003

I reproduced the issue on Fedora. After update to libimobiledevice 1.1.6 there was no issue.

USB redirection to a VM doesn't also work due to this.

Comment 3 Tomas Pelka 2016-01-28 20:35:56 UTC

Alexandros would you be able to check the fixed pkg once available.

Thanks
-Tom

Comment 4 Alexandros Gkesos 2016-01-29 07:47:38 UTC

Hello Tom,

I do not have an Apple device, but i am sure i can borrow one for few tests.
(the customer has closed the case as he was fine to use Fedora as a client)
Please let me know when the patch is available.

Thank you,
Alexandros

Comment 6 Bastien Nocera 2016-06-09 11:46:27 UTC

We would probably need to rebase to the latest stable release, instead of simply cherry picking the patch. To finish the integration, we would also need to bring in loads of gvfs patches, and possibly SELinux fixes.

Comment 7 Bastien Nocera 2016-06-09 12:05:36 UTC

See bug 1344317 for the gvfs part of the bug. Given the requirements on other components, pushing to when we will rebase gvfs.

Comment 10 Matthias Clasen 2017-03-10 18:11:48 UTC

I guess this is fixed by the gvfs rebase, then ?

Comment 11 Bastien Nocera 2017-03-13 13:03:25 UTC

(In reply to Matthias Clasen from comment #10)
> I guess this is fixed by the gvfs rebase, then ?

This isn't a gvfs bug per se, it would be fixed in the libusbmuxd/usbmuxd rebase.

Comment 12 Bastien Nocera 2017-03-14 12:25:45 UTC

Was fixed in the rebase in bug 1387253.

Comment 14 errata-xmlrpc 2017-08-01 21:28:28 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/RHBA-2017:2137