efiencrypt 1.0.1 → 1.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/{build-CUHiK1Y8.js → build-BfNzd1Cv.js} +675 -206
- package/efiencrypt +3 -3
- package/handlers.d.ts +4 -0
- package/index.js +1 -1
- package/package.json +1 -1
- package/schema.json +1 -1
- package/type.d.ts +16 -1
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
[](https://www.npmjs.com/package/efiencrypt)
|
|
4
4
|
|
|
5
|
-
**Encrypts an EFI binary using a hash derived from user-defined data (random data, disk sectors, SMBIOS fields, ...)
|
|
5
|
+
**Encrypts an EFI binary using a hash derived from user-defined data (random data, disk sectors, SMBIOS fields, EFI variables, ...). The resulting EFI can also optionally embed secure boot keys to enroll if the system is in setup mode.**
|
|
6
6
|
|
|
7
7
|
`efiencrypt` is a small utility that:
|
|
8
8
|
|
|
@@ -16,6 +16,8 @@
|
|
|
16
16
|
|
|
17
17
|
The resulting EFI can be booted with QEMU or any UEFI firmware.
|
|
18
18
|
|
|
19
|
+
It is also possible to embed secure boot keys in the resulting EFI that will be enrolled automatically before computing the hash, if the system is in setup mode. In that case, it is usually required to also sign both the input EFI binary and the resulting EFI.
|
|
20
|
+
|
|
19
21
|
## Installation
|
|
20
22
|
|
|
21
23
|
```bash
|