<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://ipxe.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://ipxe.org/feed.php">
        <title>iPXE - open source boot firmware</title>
        <description></description>
        <link>https://ipxe.org/</link>
        <image rdf:resource="https://ipxe.org/lib/tpl/doogiestpl/images/favicon.ico" />
       <dc:date>2026-04-24T07:39:17+0000</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://ipxe.org/wimboot?rev=1763211307&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.org/appnote/wimboot_architecture?rev=1632221578&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.org/howto/winpe?rev=1661290041&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.org/howto/sccm?rev=1678970166&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.org/secboot?rev=1772809148&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.org/docs?rev=1731503419&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.org/appnote/etoken?rev=1693479484&amp;do=diff"/>
                <rdf:li rdf:resource="https://ipxe.org/appnote/chainload_wds?rev=1446735488&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://ipxe.org/lib/tpl/doogiestpl/images/favicon.ico">
        <title>iPXE - open source boot firmware</title>
        <link>https://ipxe.org/</link>
        <url>https://ipxe.org/lib/tpl/doogiestpl/images/favicon.ico</url>
    </image>
    <item rdf:about="https://ipxe.org/wimboot?rev=1763211307&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-11-15T12:55:07+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>wimboot</title>
        <link>https://ipxe.org/wimboot?rev=1763211307&amp;do=diff</link>
        <description>wimboot

wimboot is a boot loader for Windows Imaging Format (.wim) files.  It enables you to boot into a Windows PE (WinPE) deployment or recovery environment.

You can use wimboot with iPXE to boot Windows PE via HTTP.  With a Gigabit Ethernet network, a typical WinPE image should download in just a few seconds.</description>
    </item>
    <item rdf:about="https://ipxe.org/appnote/wimboot_architecture?rev=1632221578&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2021-09-21T10:52:58+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:wimboot_architecture</title>
        <link>https://ipxe.org/appnote/wimboot_architecture?rev=1632221578&amp;do=diff</link>
        <description>wimboot architecture

wimboot is a boot loader that is roughly analogous to Windows' pxeboot network boot program. It lets you fetch all the relevant files over HTTP or any other supported protocol, and hands over execution to bootmgr.exe, the Windows boot manager. This page details the</description>
    </item>
    <item rdf:about="https://ipxe.org/howto/winpe?rev=1661290041&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-23T21:27:21+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:winpe</title>
        <link>https://ipxe.org/howto/winpe?rev=1661290041&amp;do=diff</link>
        <description>Network-booting Windows PE

Windows PE (WinPE) is the Windows Preinstallation Environment, used for installation and repair of Windows computers.

Using iPXE and wimboot, you can boot into Windows PE via HTTP.  You can then connect to a standard Windows file server to install a full version of Windows to the local hard disk (or to an iSCSI target).</description>
    </item>
    <item rdf:about="https://ipxe.org/howto/sccm?rev=1678970166&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-03-16T12:36:06+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>howto:sccm</title>
        <link>https://ipxe.org/howto/sccm?rev=1678970166&amp;do=diff</link>
        <description>Booting SCCM via HTTP

System Center Configuration Manager (SCCM), formerly known as Systems Management Server (SMS), is a Microsoft product used to deploy and manage large groups of Windows computers.  If you are using iPXE, then you can boot an SCCM client using HTTP, which is much faster and more reliable than the default TFTP protocol.  Over a Gigabit Ethernet network, a typical 200MB SCCM image should download in less than two seconds.</description>
    </item>
    <item rdf:about="https://ipxe.org/secboot?rev=1772809148&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-03-06T14:59:08+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>secboot</title>
        <link>https://ipxe.org/secboot?rev=1772809148&amp;do=diff</link>
        <description>UEFI Secure Boot

UEFI Secure Boot is an option that is enabled by default on most UEFI systems.  It is a security policy that is designed to allow only signed code to run at boot time.

It is important to note that UEFI Secure Boot is primarily a form of pay-to-play security theatre.  Unless you are prepared to manage your own keys (which is a laborious and often largely manual task), then there are no meaningful restrictions on the code that can be signed, or on who can perform the signing.  T…</description>
    </item>
    <item rdf:about="https://ipxe.org/docs?rev=1731503419&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2024-11-13T13:10:19+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>docs</title>
        <link>https://ipxe.org/docs?rev=1731503419&amp;do=diff</link>
        <description>Documentation

Reference material

	*  Using the iPXE command line
	*  Writing scripts using iPXE commands
	*  Configuring consoles (serial, graphical framebuffer, syslog, etc.)
	*  Using cryptography for HTTPS or code-signing
	*  List of all iPXE commands
	*  List of all iPXE settings
	*  List of all iPXE build options

[Some books]

Howto guides

Starting iPXE</description>
    </item>
    <item rdf:about="https://ipxe.org/appnote/etoken?rev=1693479484&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2023-08-31T10:58:04+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:etoken</title>
        <link>https://ipxe.org/appnote/etoken?rev=1693479484&amp;do=diff</link>
        <description>UEFI Secure Boot signing using a DigiCert eToken

UEFI Secure Boot requires UEFI binaries to be signed by Microsoft.  This page documents the work in progress to obtain signed versions of iPXE and wimboot.

EV Code Signing Certificate

Microsoft requires submitted UEFI binaries to be signed using an EV Code Signing certificate.  These can be obtained from providers such as</description>
    </item>
    <item rdf:about="https://ipxe.org/appnote/chainload_wds?rev=1446735488&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-11-05T14:58:08+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>appnote:chainload_wds</title>
        <link>https://ipxe.org/appnote/chainload_wds?rev=1446735488&amp;do=diff</link>
        <description>Chainloading Windows Deployment Services

Windows
Deployment Services (WDS) is a set of services and APIs to
facilitate Windows operating system installation by using PXE, DHCP
and TFTP to bootstrap WinPE, the
Windows
Preinstallation Environment. You can think of it as providing
similar functionality to iPXE with server-side scripting, where
clients are served boot configuration and images based on various
criteria, such as hardware architecture.</description>
    </item>
</rdf:RDF>
