Windows 11/Future for Us

[george1421]

@richiestuff I also looked into this issue. I was able to work up a workflow were you can use a custom self signed certificate. https://forums.fogproject.org/topic/15888/imaging-with-fog-and-secure-boot-poc

I looked quickly at the shim approach, but the issue is we need to sign ipxe binaries too.

Clonezilla took the approach to use stock ubuntu or debian kernels so they could use their signed stuff. Nothing wrong with that and could be an approach for FOG, except of course for iPXE.

Thank you for providing an additional path for secure booting. I wasn’t aware of that approach, well done.

[Sebastian Roth]

@richiestuff said in Windows 11/Future for Us:

SHIM review board and lots of infos on the process can be found here:
https://github.com/rhboot/shim-review

Nice! Didn’t know about this yet.

Though looking through the question template I fear we might not be considered to get our shim signed:

• Who is the primary contact for security updates, etc.? Name, Position, Email address, PGP key fingerprint (Key should be signed by the other security contacts, pushed to a keyserver like keyserver.ubuntu.com, and preferably have signatures that are reasonably well known in the Linux community.)
• Who is the secondary contact for security updates…
• … MANY questions about technical details which do not apply to iPXE I guess …

And there is another hurdle:

Note that we really only have experience with using GRUB2 on Linux, so asking us to endorse anything else for signing is going to require some convincing on your part.

Looking at others going through this process is kind of fun but I am not sure we (as a community) can handle this.

[Wayne Workman]

Reading through this thread, I’d say we need a champion to help the FOG Project with the money and process. Here is where any for-profit company reading this should consider helping with two things.

• Donate some man-hours for a person to work with the FOG devs on this
• Donate the money to cover the cost.

Personally, I think it should be Microsoft who helps. If FOG is unable to easily deploy Windows 11 due to secureboot related difficulties, School Districts will have further reason to just buy Chromebooks instead of Windows PCs.

[fry_p]

Just as an update to this post…We proceeded with moving away from FOG for the time being. We now use a paid solution. It was not a decision we made lightly and ultimately was due to ease of secure booting and bitlocker as well as a more streamlined way to push apps and scripts. It’s really not fair to compare these products because of the volunteer driven, open source free nature of FOG vs. a company who can pay the money easily for certs.

However, I want FOG to find a champion like @Wayne-Workman said. I have been with two school districts who relied on FOG for many years. I know other districts who could not function without FOG right now as well. I still want to help where I can in the Forums though I have been inactive recently, I plan to change that. Just out of curiosity, how much would it cost to have Microsoft to sign the certs?

[Wayne Workman]

@fry_p said in Windows 11/Future for Us:

Just out of curiosity, how much would it cost to have Microsoft to sign the certs?

Microsoft should consider doing this for FOG as a donation.

[Sebastian Roth]

@fry_p said in Windows 11/Future for Us:

I still want to help where I can in the Forums though I have been inactive recently, I plan to change that.

Sounds great! You are more than welcome to engage.

Just out of curiosity, how much would it cost to have Microsoft to sign the certs?

I have no idea.

[fry_p]

@sebastian-roth Is this what we would have to do for the signing? This does seem over the top, but then again, I could be looking at the wrong thing.

[Sebastian Roth]

@fry_p I am not sure but sounds reasonable. Here is the fun part of the document:

4. Code submitted for UEFI signing must not be subject to GPLv3 or any license that purports to give someone the right to demand authorization keys to be able to install modified forms of the code on a device. Code that is subject to such a license that has already been signed might have that signature revoked. For example, GRUB 2 is licensed under GPLv3 and will not be signed.

[Wayne Workman]

It’s got a special section just for iPXE.

If your submission contains iPXE functionality, then additional security steps are required. Previously, Microsoft has completed an in depth security review of 2Pint’s iPXE branch. In order for new submissions with iPXE to be signed, they must complete the following steps:

    Pull and merge from 2Pint's commit: http://git.ipxe.org/ipxe.git/commitdiff/7428ab7  
    Get a security review from a verified vendor. Refer vendor to the iPXE Security Assurance Review blog post. Emphasis of the review should be on:
        NFS functionality being removed
        Wireless functionality being removed
        Non-UEFI loaders are not included
        Ensuring all known reported security problems are fixed (identified in the iPXE Security Assurance Review blog post).
    Share the specific commits that are made to the project, allowing Microsoft to ensure the expected changes are made.

[fry_p]

I saw both of those requirements. This doesn’t look promising. I guess now it is less about the price and more about the ridiculous hoops to jump through. Also the GPLv3 thing is killer for us.

[putrzop]

Get an EV certificate from the certificate vendor of your choice and build you own flavor of the SHIM,

[putrzop]

Microsoft should consider doing this for FOG as a donation.. .