What it actually means and if it's possible to create an identifier for pyatv is unclear to me. The identifier XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX is part of the response from the Apple TV. Gonna continue by incorporating my changes into the proxy in order to intercept what is sent between the ATV and Shortcuts.įörvalđ4:32:54.055046+0200 rapportdđ489: IdentityProofsVerify RP: yes, 0x0 įörvalđ4:32:54.057195+0200 rapportdđ489: IdentityProofsVerify HKO: kAuthenticationErr (Signature verify failed)įörvalđ4:32:54.057415+0200 rapportdđ489: IdentityProofsVerify check HKU: ID XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXXįörvalđ4:32:54.074815+0200 rapportdğindPairedPeer found: 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX', HAP, 4 msįörvalđ4:32:54.075900+0200 rapportdđ489: IdentityProofsVerify verify HKU: ID XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX, kAuthenticationErr (Signature verify failed)įörvalđ4:32:54.076215+0200 rapportdđ488: Invalidatingįörvalđ4:32:54.076491+0200 rapportdĜLinkCnx-1488: Invalidatingįörvalđ4:32:54.076638+0200 rapportdĜLinkCnx-1488: Abort reads: kCanceledErr (Invalidated (I))įörvalđ4:32:54.076957+0200 rapportdđ488: # Receive failed: kCanceledErr (Invalidated (I)) Will work on that, at least to the extent that I understand how it works.Ĭan't stress this enough: this is good progress, but it's gonna be a loooong time until I have something usable. I have a few bugs and missing features in my OPACK implementation, so I have a few decoding issue. I'm gonna share as much as possible publicly in case someone wants to help reverse engineering this protocol.įörvalĐ9:00:55.468389+0200 rapportdđ36: PairSetup next (229 bytes)įörvalĐ9:00:55.468539+0200 rapportdĜLinkCnx-136: Pair-setup client M6 - exchange response It doesn't work yet, it's just a start and my intention is to lift this work in to pyatv and start working on support for pairing. I have started hacking on an implementation outside of pyatv as a test. So this is quite uncharted territories and will probably need a lot of work. Not much is written about this protocol from what I have gathered. Perhaps there are other interesting features this can be used for as well (e.g. Preferably I would like a generic implementation of the protocol next to the other ones and use that to implement #303. I suspect that this protocol is used by Handoff and Continuity as well. I'm especially interested in the latter in order to implement #303. I'm not entirely sure what all the use cases for it are, but I do know that this is the protocol used by the Apple TV widget in action center since iOS 13 (prior to that MRP was used) and it is also used to launch apps from Shortcuts. Apparently there's a protocol called "companion link", announced as the zeroconf service _companion-link._tcp.local. As it turns out, there can never be too many protocols.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |