|
1 | 1 | # Firmware security |
2 | 2 |
|
3 | 3 | The firmware security feature can be configured by setting `CONFIG_SECURITY=1` |
4 | | -in the `src/board/system76/[board]/board.mk` file. This feature prevents |
| 4 | +in the `src/board/system76/<board>/board.mk` file. This feature prevents |
5 | 5 | programming the EC firmware at runtime, unless the EC is unlocked with the |
6 | 6 | `system76-ectool security unlock` command. After this, on the next reboot, the |
7 | | -EC will respond to the SPI and reset commands. On boards where the `ME_WE` GPIO |
8 | | -exists, it will be set high when the EC security state is unlocked. |
| 7 | +EC will respond to the SPI and reset commands. |
| 8 | + |
| 9 | +This feature will drive the `ME_WE` pin high when the state is unlocked. On |
| 10 | +Intel hosts, this pin is connected to `HDA_SDO` and will disable security |
| 11 | +policies set in the flash descriptor. |
| 12 | + |
| 13 | +- `HDA_SDO`: Flash Descriptor Security Override |
9 | 14 |
|
10 | 15 | Other firmware components can use this state to perform their own locking and |
11 | | -unlocking primitives. For example, in `coreboot`, flash regions may be locked |
12 | | -when the EC security state is locked. In `EDK2`, a physical presence dialog may |
13 | | -be shown when the EC security state is unlocked. |
| 16 | +unlocking primitives. For example, in coreboot, flash regions may be locked |
| 17 | +when the EC security state is locked. In the UEFI payload, a physical presence |
| 18 | +dialog may be shown when the EC security state is unlocked. |
0 commit comments