You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am a maintainer of the AirPlay (mirror and Audio-streaming) server UxPlay http://github.com/FDH2/UxPlay which
acts like an AppleTV. Its codebase is C and derives from ShairPlay/AirPlayServer/RpiPlay.
UxPlay handles legacy pairing, but this is now off by default and the Features bit for this and password is turned off. With these features enabled the client initiates pair-pin-start etc. and when clients are managed with MDM they may request pair-pin-start even if the server does not require a password.So I am considering adding it, but it has never been in the ancestral codebase of ShairPlay from which our implementation derives.
Am I right that your codebase is only implementing it for the client but not the server?
will I find enough information in you codebase to handle the (C implementation ) of pair-setup-pin on the server before pair verify?
Grateful for any suggestions.
Uxplay with the features bit (27) for "supports legacy pairing" turned on currently just does:
pair_setup
pair_verify 1
pair_verify 2
fp_setup
etc
I suppose that pair-pin-setup replaces pair-setup ?
Hi
I hope you dont mind me asking for any advice.
I am a maintainer of the AirPlay (mirror and Audio-streaming) server UxPlay http://github.com/FDH2/UxPlay which
acts like an AppleTV. Its codebase is C and derives from ShairPlay/AirPlayServer/RpiPlay.
UxPlay handles legacy pairing, but this is now off by default and the Features bit for this and password is turned off. With these features enabled the client initiates pair-pin-start etc. and when clients are managed with MDM they may request pair-pin-start even if the server does not require a password.So I am considering adding it, but it has never been in the ancestral codebase of ShairPlay from which our implementation derives.
Am I right that your codebase is only implementing it for the client but not the server?
will I find enough information in you codebase to handle the (C implementation ) of pair-setup-pin on the server before pair verify?
Grateful for any suggestions.
Uxplay with the features bit (27) for "supports legacy pairing" turned on currently just does:
pair_setup
pair_verify 1
pair_verify 2
fp_setup
etc
I suppose that pair-pin-setup replaces pair-setup ?
@fduncanh
The text was updated successfully, but these errors were encountered: