Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for macOS 13.6.5 #38

Open
ElioDiNino opened this issue Mar 15, 2024 · 3 comments · May be fixed by #41
Open

Support for macOS 13.6.5 #38

ElioDiNino opened this issue Mar 15, 2024 · 3 comments · May be fixed by #41

Comments

@ElioDiNino
Copy link

I know it was released only a week ago, but want to put an issue on the board so that a plan for 13.6.5 can be made :)

@0xdevalias
Copy link
Contributor

Ventura 13.6.5 is out now and I forgot about Beeper and upgraded. If someone wants to put the new lines into offsets.go and rebuild, that would be awesome:

// macOS 13.6.5
hexToByte32("253e81362b42a1a5db4270a0f7b55f3f7f0b0ed4c8e3f8a45660d22e3025a971"): offsets_13_6,

Originally posted by @Marckus in #9 (comment)

@0xdevalias
Copy link
Contributor

You could try the automatic scripts mentioned in this thread:

And/or upload the needed binary so that someone can potentially reverse the offsets.

@Marckus
Copy link

Marckus commented Mar 18, 2024

You could try the automatic scripts mentioned in this thread:

* [Automatically find/calculate offsets in binaries that haven't been manually reversed #9](https://github.com/beeper/mac-registration-provider/issues/9)

And/or upload the needed binary so that someone can potentially reverse the offsets.

Thanks. I'm extremely new to GitHub, so please forgive any ignorance here. I had thought that the two lines of code that I had included in my comment above was all that was needed. Nothing else changed to my knowledge, as I added those two lines to my local copy of offsets.go and built the app locally and it ran and it works fine. I'm not familiar with how to get those lines into the GitHub repository so I made my comment about it.

@ElioDiNino ElioDiNino linked a pull request Mar 19, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants