-
Notifications
You must be signed in to change notification settings - Fork 10
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
PRK invaild with long string of characters #7
Comments
Hi @JaxsonPina - Yes, expected behavior after Escrow Buddy triggers a new key to be generated and escrowed would be that the "Personal Recovery Key Validation" would become If after installing and configuring Escrow Buddy, logging in, and updating Jamf inventory on the affected Mac, the key is still invalid/unchanged, I would be interested in seeing your logs. |
Hi @JaxsonPina - Did you discover anything from the logs? |
Thanks for following up, but we haven’t deployed it yet. We did update JAMF to 11.4.2 not so long ago and I will verify those with the characters after we get the OK, it should be sometime next week.
From: Elliot Jordan ***@***.***>
Date: Thursday, May 30, 2024 at 11:29ter
To: macadmins/escrow-buddy ***@***.***>
Cc: JaxsonPina ***@***.***>, Mention ***@***.***>
Subject: Re: [macadmins/escrow-buddy] PRK invaild with long string of characters (Issue #7)
Hi @JaxsonPina<https://github.com/JaxsonPina> - Did you discover anything from the logs?
—
Reply to this email directly, view it on GitHub<#7 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFTTI3WB776CVXQFVKF2YELZE5AWDAVCNFSM6AAAAABCLHSNAWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZHE2DQNBYGA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Interesting. Strings beginning with @k3vmo, I notice that there aren't any Escrow Buddy logs shown. Did the user of that Mac log out or restart within the 24 hours prior to the log collection? And was the |
Yes, the systems had been logged out of, restarted multiple times over a week with no change but I too figured it was encryption related.
Turns out it must have been the certificate got corrupted during the migrations.
I created a new FV configuration in Jamf & saved to recreate the cert. Deployed it and it worked after just a few minutes. All systems got valid keys after doing so. If you see that random string id suggest recreating the FV payload.
|
Summary
PRK invalid status
does Escrow Buddy fix the invalid PRK that have the long strings of characters in the PRK field when you click on it.
Unknown do get fixed, its just the ones with the long characters
Additional Context
The text was updated successfully, but these errors were encountered: