Categories

  • 13k Topics
    115k Posts
    K

    @Tom-Elliott
    Hi Tom,
    We’re on school holidays in Austria at the moment – I’m not at school right now. At the end of August, I’ll have to install the new image on all the pupils’ PCs. Once that’s done, I’ll be able to start trying things out again. Have a lovely summer, Alexander

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    J

    I remplaced grubx64 by grubnetx64 (not sure if needed but was recommanded for PXE) and create a “grub” directory in tftpboot with “grub.cfg” inside.
    Grub signed look for cfg file in a subdir called “grub” by default.

    cp /usr/lib/grub/x86_64-efi-signed/grubnetx64.efi.signed /tftpboot/grubx64.efi mkdir /tftpboot/grub chmod -R a+rX /tftpboot/grub

    I get grub menu.

    update (10 am) :
    I copied snponly.efi in grub directory and signed it with the FOG-MOK key I generated before.

    sbsign --key /root/secureboot/FOG-MOK.key --cert /root/secureboot/FOG-MOK.crt /tftpboot/snponly.efi --output /tftpboot/grub/snponly.efi

    I end with “error ; bad shim signature”.
    I think I need to import the key on the computer with command “mokutil --import /chemin/vers/FOG-MOK.der”

    I keep on searching…

    2nd update (12:30 am):

    To enroll key :

    cp /usr/lib/shim/mmx64.efi.signed /tftpboot/mmx64.efi

    and in tftpboot/grub/grub.cfg

    menuentry 'Enroll MOK' { insmod tftp insmod chain chainloader (tftp,192.168.69.10)/mmx64.efi boot } menuentry 'Boot FOG (iPXE)' { insmod efinet insmod tftp insmod chain net_bootp chainloader (tftp,192.168.69.10)/grub/snponly.efi boot }

    Copy the .der on usb key, put it on the computer, run “Enroll from disk” in pxe grub menu.
    Reboot and run “Boot FOG”…
    And at least I have the FOG menu ! 😎
    I think I’m in the right way. 😅

    Let’s keep on working.

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    Tom ElliottT

    @Valer Thanks for the report and the writeup, that’s a good catch. You’re right about the cause. Debian 13 dropped the sysv-rc-conf package since it’s fully on systemd now, so the installer chokes trying to apt-get it. We never actually use that tool on a systemd system anyway, it only ever got called on the old non-systemd paths, so it was just dead weight on Trixie.

    I pushed a fix to working-1.6. It leaves the package off the list on Debian 13 and up, and it also strips it out of a cached .fogsettings so an in-place upgrade doesn’t drag it back in. Older Debian keeps installing it like before so nothing changes there.

    If you want to get moving before you pull the update, you can either grab the latest working-1.6 and rerun the installer, or just open /opt/fog/.fogsettings and delete sysv-rc-conf from the packages line, then run the installer again. Either one gets you past it.

    Let me know if you hit anything else on Trixie.

109

Online

12.7k

Users

17.6k

Topics

156.7k

Posts