Bug#840931: Stale pairing records may be left

[Tino Mettler]

Hi,

I created a separate bug for this issue:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851139

Regards,
Tino

Bug#840931: Stale pairing records may be left

[Tino Mettler]

Hi,

is anybody with upload permissions reading this? There are roughly 2
weeks left to upload a fixed package to sid so it can migrate to
testing before the full freeze.  If nobody else does, I'll prepare a
fixed package with the mentioned patches and the removal of stale
pairing entries which can be uploaded by someone with upload
permsissions.  My key (ADA5A11B2B805596C78E9067E806E77FF82155BC) is in
the keyring, so granting upload permissions for me would work, too.

Regards,
Tino


signature.asc
Description: Digital signature

Bug#840931: Stale pairing records may be left

[Tino Mettler]

On Mon, Jan 09, 2017 at 15:34:46 +0100, Tino Mettler wrote:

> I suggest a least a NEWS entry instructing the user how to remove old
> pairing entries. We could also try to check for broken pairing entries
> in an automated way. I'll check if I can reproduce the problem and cook
> up a script.

Hi,

a broken pairing entry in /var/lib/lockdown contains this, as expected:

DeviceCertificate



The DeviceCertificate contains no data in case of a broken entry. This
should be easy to detect. Here is an example using xmlstarlet:

if test -z $(xmlstarlet sel -t -v 
'//key[.="DeviceCertificate"]/following-sibling::data[1]'
74f06bdcba12be895b317ff02107cf4f15b8b0d0.plist) ; then
rm foo.plist
fi

This would require a dependency to xmlstarlet, though.

Regards,
Tino

Bug#840931: Stale pairing records may be left

[Tino Mettler]

Hi,

according to
https://github.com/libimobiledevice/libimobiledevice/issues/413#issuecomment-258321151
stale paring data might be left.

If I got this right, in this case the user might still not be able to
access the iOS device even with the above patches applied. I'll try to
check if I can reproduce this with old pairing entries.

I suggest a least a NEWS entry instructing the user how to remove old
pairing entries. We could also try to check for broken pairing entries
in an automated way. I'll check if I can reproduce the problem and cook
up a script.

Regards,
Tino