WDS, iPXE, DHCP and SecureBoot
|
2017-01-13, 18:18
Post: #7
|
|||
|
|||
RE: WDS, iPXE, DHCP and SecureBoot
(2017-01-13 07:13)abos_systemax Wrote: Since we have an EV certificate; (and i've seen the instruction) how common is it that Microsoft will allow our signed iPXE to be 'available' for secure boot and will it be immediately available after Microsoft allows it, or will it be allowed in further firmwares? As with all certificates the "target" will not need any update since they use signatures, so that is safe. If you have a EV certificate for code signing, then you can try and get MS to sign a version of iPXE, I only know of one instance of it being done, and it was no easy task. You should probably come online on IRC and talk to mcb30 or Andreas about that process. Use GitHub Discussions VRAM bin |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
WDS, iPXE, DHCP and SecureBoot - abos_systemax - 2017-01-11, 16:24
RE: WDS, iPXE, DHCP and SecureBoot - NiKiZe - 2017-01-11, 20:00
RE: WDS, iPXE, DHCP and SecureBoot - abos_systemax - 2017-01-12, 09:35
RE: WDS, iPXE, DHCP and SecureBoot - ndog - 2017-01-12, 12:10
RE: WDS, iPXE, DHCP and SecureBoot - NiKiZe - 2017-01-12, 19:11
RE: WDS, iPXE, DHCP and SecureBoot - abos_systemax - 2017-01-13, 07:13
RE: WDS, iPXE, DHCP and SecureBoot - NiKiZe - 2017-01-13 18:18
|
User(s) browsing this thread: 3 Guest(s)