3 ms·
Interesting project although the drawback seems to be that the maintenance is pretty high since it uses the hardcoded memory addresses to dump the key for each
by sdfhbdf 6y ago
Interesting project although the drawback seems to be that the maintenance is pretty high since it uses the hardcoded memory addresses to dump the key for each Spotify version. I understand it requires from the maintainer after each update, which are frequent since Spotify has a well-developed Continuos Delivery [0], to reverse engineer the memory address and commit it to this repo.
[0]: https://www.youtube.com/watch?v=5Ycb7jlZGkU https://www.youtube.com/watch?v=5Ycb7jlZGkU
- yjftsjthsd-h 6y agoIf picking up memory addresses can be automated, then would be fairly hilarious to put that into a CI system so that Spotify automatically pushes to release... and then this immediately automatically pulls it and builds a release to match:)
- Orphis 6y agoSpotify can also chose to prevent older clients to connect and only allow the latest one with new protections rendering this attack useless.