Giter Club home page Giter Club logo

droidairplay's People

Contributors

fgp avatar pentateu avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

droidairplay's Issues

fpaeskey vs. rsaaeskey

From what I could see recently with various challenge exchange in AirPlay, and as noticed on the comment at
https://github.com/pentateu/DroidAirPlay/blob/master/src/main/java/nz/co/iswe/android/airplay/audio/RaopAudioHandler.java#L418 the AES Key comes in FairPlay encrypted instead of RSA encrypted and on a different key than it used to be. The code at https://github.com/pentateu/DroidAirPlay/blob/master/src/main/java/nz/co/iswe/android/airplay/audio/RaopAudioHandler.java#L484 only expects parsing the original rsaaeskey but as per the previous comments should also be handling the fpaeskey.

Do you guys have any idea how to go about decrypting that key given it's no longer RSA encrypted? I've seen many documents online about collecting the information sent by the fp-setup phases (as potential dynamic keys) used to decrypt the AES key later on, so rather than simply faking the response as the app does right now, we'd need to interpret those FPLY bytes that come in to be able to store the appropriate information to use when seeding the FP decryption algorithm used to decrypt the AES key late on.

Just thought I'd file this here to start a discussion around it.

Importe & Run on Android Studio

Hello everyone,

Is it possible to have a version that we can import on Android Studio ?
If someone did it, it would be very cool !

Thank you !

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.