Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cmd:imgtrust [2012/03/22 14:31] mcb30 |
cmd:imgtrust [2012/03/24 20:32] mcb30 |
||
|---|---|---|---|
| Line 23: | Line 23: | ||
| Require the use of trusted images. When trusted images are required, any attempts to execute an untrusted image will fail. All images are untrusted by default. To become trusted, an image must be verified using the ''[[:cmd:imgverify]]'' command. | Require the use of trusted images. When trusted images are required, any attempts to execute an untrusted image will fail. All images are untrusted by default. To become trusted, an image must be verified using the ''[[:cmd:imgverify]]'' command. | ||
| - | If the ''--allow'' option is specified then the trusted images will no longer be required, and untrusted images may be executed. | + | If the ''%%--allow%%'' option is specified then the trusted images will no longer be required, and untrusted images may be executed. |
| - | If the ''--permanent'' option is specified, then the image trust requirement will be made permanent. Any future attempts to change the image trust requirement will fail. For example: | + | If the ''%%--permanent%%'' option is specified, then the image trust requirement will be made permanent. Any future attempts to change the image trust requirement will fail. For example: |
| iPXE> imgtrust # Require trusted images | iPXE> imgtrust # Require trusted images | ||
| Line 63: | Line 63: | ||
| There is no way to use trusted images without using an embedded script.((The embedded script is required because there is no standard way to obtain the signature for an image corresponding to the DHCP [[:cfg:filename]].)) | There is no way to use trusted images without using an embedded script.((The embedded script is required because there is no standard way to obtain the signature for an image corresponding to the DHCP [[:cfg:filename]].)) | ||
| - | The ''imgtrust'' command only prevents the direct execution of untrusted images by iPXE. An untrusted image may still be used as, for example, the initrd for a trusted kernel image. You can use the ''[[:cmd:imgverify]]'' command to explicitly verify any such additional images. | + | The ''imgtrust'' command only prevents iPXE from directly executing an untrusted image. For example: when executing a Linux kernel image, ''imgtrust'' will prevent the execution of an untrusted kernel image, but will not prevent the use of an untrusted initrd. If you want to ensure that any additional images (such as an initrd) are also trusted, then you must explicitly verify them using the ''[[:cmd:imgverify]]'' command. |
