[1]: http://useyourloaf.com/blog/2012/02/07/remote-packet-capture...
[1]: http://useyourloaf.com/blog/2012/02/07/remote-packet-capture...
I hadn't seen the packet capture thing before, but after reading the slides a quick google search turned up the link to the apple dev util that you referenced.
I'm also not sure how big of deal the "doesn't require developer mode" thing is, since the issues he raises require pairing records, and I believe you can enable developer mode if you have that much access. I've never had the device ask for confirmation when I turned on developer access.
So does this mean a private key ripped off a paired Bluetooth speaker ends up pwning me? If you are taking case of IT, I think a valid hacking scenario also needs to be considered. Furthermore, all the data in available un-encrypted. I don't know how comfortable I would be with that. Also, once trusted means permanently a slave?
The "pairing" refers to when you connect via a USB cable and say "trust this computer". (The iOS device must be unlocked.)
An encrypted copy of the some keys are sent to the computer. These allow the iOS device to decrypt data that normally can only be decrypted after the passcode is entered. (Making it possible to back up the device without entering the passcode.) Those encrypted keys can only be decrypted by a trusted computing module on that specific device. So you are kinda screwed if someone has both your laptop and your iphone, and they have Apple-level access to the iphone. I recommend using file vault or other full disk encryption to protect your laptop.
http://www.apple.com/ipad/business/docs/iOS_Security_Feb14.p...