We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
NOTE: I have not tested to see if this is unique to MacOS or if this is also in Linux
We use a server to retrieve passcodes using recovery keys and when using:
sudo dislocker-metadata -V /dev/disk4s4 | grep Recovery
it returns 2 different keys with the same time stamp (i changed the last digits for security but every character in the key is different):
Tue Jan 23 14:23:59 2024 [INFO] Recovery Key GUID: '4C672E5A-D0DB-4749-BD11-123456789012' Tue Jan 23 14:23:59 2024 [INFO] Recovery Key GUID: '42FC9468-612A-4348-BF31-123456789012'
I was wondering is this a bug? Which key is valid for me to enter into our server to get the decrypt password?
The text was updated successfully, but these errors were encountered:
Although multiple "Recovery Key GUIDs" were returned, is there any pattern? Is the last Recovery Key GUID always the correct one?
Sorry, something went wrong.
Do you know how to generate multiple 'Recovery Key GUIDs'?
No branches or pull requests
NOTE: I have not tested to see if this is unique to MacOS or if this is also in Linux
We use a server to retrieve passcodes using recovery keys and when using:
sudo dislocker-metadata -V /dev/disk4s4 | grep Recovery
it returns 2 different keys with the same time stamp (i changed the last digits for security but every character in the key is different):
I was wondering is this a bug? Which key is valid for me to enter into our server to get the decrypt password?
The text was updated successfully, but these errors were encountered: