WDS, iPXE, DHCP and SecureBoot
|
2017-01-12, 19:11
Post: #5
|
|||
|
|||
RE: WDS, iPXE, DHCP and SecureBoot
(2017-01-12 09:35)abos_systemax Wrote: What we were doing in the old situation, was redirecting DHCP to WDS (next-server to the WDS server) and then set the boot program from WDS to pxelinux.cfg; is there a similar method known for IPXE? Again SecureBoot is not relevant in pcbios, just use a filename for wds.efi when the requested arch is efi, and then if you wish chain from that wds menu into ipxe. Current wimboot is actually signed by MS, the issue with ipxe is that MS does not like what you can do inside of ipxe, and also that the process for signing ipxe needs to be automatic to be officially available. Not even grub is signed by MS, instead most distros rely on shim.efi which have been signed by MS. 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)