pypush VS pypush

It’s written in Go and hasn’t been opened yet but it’s heavily based around this project: https://github.com/JJTech0130/pypush

neither this nor search is very much a hard problem as it’s been solved many times over already. The harder part is that beeper never reverse engineered anything, they bought the POC from a high school kid that did it as a project: https://github.com/JJTech0130/pypush meaning they never had the ability to do it in the first place

This should have been obvious to anyone who saw the code where it simply contained the raw literal string `FAIRPLAY_PRIVATE_KEY = b64decode(“…”)`. I suppose now we’ll see how accurate the commenter’s claim “if this becomes a problem, I know how to generate new keys” is.

https://github.com/JJTech0130/pypush/blob/main/albert.py#L16

I had copied it from JJ’s official GitHub website https://github.com/JJTech0130/pypush

Beeper open-sourced their reverse engineering effort, which means that there will now be a significant ongoing community effort to maintain the solution. It would be very difficult to stop the Beeper solution from working without also breaking iMessage clients running on older versions of MacOS or iOS. Apple may be able to keep new iMessage features locked up, but it would probably only be a matter of time before the community manages to reverse engineer those features, as well.

Here's the code that Beeper bought for this: https://github.com/JJTech0130/pypush

He also has to fake being an apple device using real device identifiers. https://github.com/JJTech0130/pypush/blob/main/emulated/data.plist

pypush, which was formerly at github.com/beeper/pypush (it still redirects) added a notice about being acquired by Beeper yesterday. Coincidence? We can only wait and see.