Sneed-Group/pypush-plus-plus
1
0
Fork 0
mirror of https://github.com/Sneed-Group/pypush-plus-plus synced 2024-12-23 11:22:42 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix spelling lol

Browse source
This commit is contained in:
JJTech 2023-07-31 15:12:47 -04:00 committed by GitHub
parent 84f9c114f7
commit 31102d6b53
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -1,6 +1,6 @@
# pypush # pypush
`pypush` is a POC demo of my recent iMessage reverse-engineering. `pypush` is a POC demo of my recent iMessage reverse-engineering.
It can currently register as a new device on an Apple ID, set up encryption keys, and ***send and recieve iMessages***! It can currently register as a new device on an Apple ID, set up encryption keys, and ***send and receive iMessages***!
`pypush` is completely platform-independent, and does not require a Mac or other Apple device to use! `pypush` is completely platform-independent, and does not require a Mac or other Apple device to use!
@ -28,6 +28,6 @@ This is only necessary during initial registration, so theoretically you can reg
to another device that doesn't support the Unicorn emulator. Or you could switch out the emulator for another x86 emualtor if you really wanted to. to another device that doesn't support the Unicorn emulator. Or you could switch out the emulator for another x86 emualtor if you really wanted to.
### Public key caching ### Public key caching
iMessage will cache public keys. If you get decryption errors in pypush or can only send and not recive messages from another device, iMessage will cache public keys. If you get decryption errors in pypush or can only send and not receive messages from another device,
try logging out and back into iMessage on that device, forcing it to refresh it's key cache. Alternatively, you can wait and the cache should try logging out and back into iMessage on that device, forcing it to refresh it's key cache. Alternatively, you can wait and the cache should
expire eventually. expire eventually.