-
Notifications
You must be signed in to change notification settings - Fork 13
Decryption of provisioned device #79
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
Comments
In order to decrypt in a RMA-style situation, you must record the device private key - and this can only be done as part of initial provisioning. Automating this is on my roadmap. If you cannot wait for that release, add an additional fastboot command before setting the LED status:
Add something like:
Then, use that key as the LUKS passphrase when you mount the storage on a host. In practice, depending on the sort of failure involved, this may require you to dismount the eMMC and re-mount it on a media accessible by another machine. As ever - this would have you capture sensitive key material - you must take precautions to prevent unauthorised and unnecessary accesses. |
Thank you @tdewey-rpi - that's very helpful. Is there any way to support such development to help accelerate delivery of such functionality? |
Not directly, I'm afraid - but given your response I'm going to classify this issue as high priority, and apportion time accordingly. |
If there's GitHub Sponsors / Open Collective / etc. setup for this project I'd be happy to sponsor some further development. Either way, thank you for the information and all the work in creating this! |
While I appreciate the thanks, I must point out that I'm a full-time employee of Raspberry Pi, and as such the knowledge that this will help our products better meet your needs is enough. |
Thank you, will give it a try! |
Hi,
If I use this provision a device, and then the device malfunctions and I want to investigate it by decrypting the data - what's the process to decrypt it?
Thank you!
The text was updated successfully, but these errors were encountered: