-
-
Notifications
You must be signed in to change notification settings - Fork 113
Fix decryption on Ventura 13.6 for bare-metal M1 instances #214
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
base: main
Are you sure you want to change the base?
Conversation
|
Hey! Sorry for taking a while to respond. Your changes look good but I've left one suggestion to improve, if you can fix it I'll be happy to merge. Also tip: if you install pre-commit and the checks as detailed in the readme, you can check these rules locally 🙂 |
|
Hi, I don't see any review comments? Could you point me in the right direction? Thanks |
| "/usr/bin/security find-generic-password -l 'BeaconStore' -w" | ||
| ) | ||
| if not key_in_hex: | ||
| raise ValueError("Empty output from security -w") # noqa: EM101, TRY003, TRY301 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix these linter errors instead of ignoring them
|
Sorry, forgot to publish them 😅 |
|
I'll push changes this weekend, thanks! |
While running Find My decryption on a bare-metal M1 instance (Ventura 13.6) on Scaleway, I encountered an issue: the AES key resolved as empty (key_in_hex: ''), causing decryption to fail. Surprisingly, no password prompt appeared, even though I was connected via VNC (not SSH).
This patch adjusts the authentication/decryption flow, which resolved the issue in my environment. Decryption now completes successfully on Ventura 13.6 on bare-metal M1 instances.
It is only a fallback, so it shouldn't impact any other users.