Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    12k Topics
    114k Posts
    N

    On a ubuntu server, I fail to update FOG from 1.5.10.1798 to 1.5.10.1870 :

    before the update:

    $ dpkg -l | grep mysql-client ii mysql-client 8.0.46-0ubuntu0.22.04.2 all MySQL database client (metapackage depending on the latest version) ii mysql-client-8.0 8.0.46-0ubuntu0.22.04.2 amd64 MySQL database client binaries ii mysql-client-core-8.0 8.0.46-0ubuntu0.22.04.2 amd64 MySQL database core client binaries

    then:

    $ sudo ./installfog.sh [...] * Checking package: liblzma-dev...............................OK * Checking package: m4........................................OK * Checking package: mariadb-server............................OK * Checking package: mysql-client..............................Failed! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! The installer was not able to run all the way to the end as !! !! something has caused it to fail. The following few lines are !! !! from the error log file which might help us figure out what's !! !! wrong. Please add this information when reporting an error. !! !! As well you might want to take a look at the full error log !! !! in /tmp/fogproject-1.5.10.1870/bin/error_logs/fog_error_1.5.10.1870.log !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ii libc6:amd64 2.35-0ubuntu3.13 amd64 GNU C Library: Shared libraries ii liblzma-dev:amd64 5.2.5-2ubuntu1 amd64 XZ-format compression library - development files ii m4 1.4.18-5ubuntu2 amd64 macro processing language ii mariadb-server 1:10.6.23-0ubuntu0.22.04.1 all MariaDB database server (metapackage depending on the latest version) dpkg-query: no packages found matching mysql-client

    and if I check the packages:

    $ dpkg -l | grep mysql-client

    It’s not there anymore.

  • Get the latest news on what's happening.
    Security Advisories
    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.
    General Tutorials
    2k Topics
    19k Posts
    K

    @Florent Hi Florent,

    I actually have been meaning to look into this some more, but the likely answer is no, or at least, not entirely. The way that support works is, you download a signed iPXE 2.0 binary from iPXE and a copy of their signed shim. That shim is signed with the Microsoft keys and trusts the iPXE signing keys. What this means in practical terms is, all the steps above would still need to occur, it’s just that the signing of the iPXE binary is managed by iPXE, and you don’t need to enroll a key to boot iPXE.

    That said, I would imagine this only covers you for booting iPXE, any chainloaded binaries would still need to be signed either with Microsoft’s key or a MOK key you’ve enrolled on the machine. In FOG’s case this means the FOS kernel has to be signed and trusted on the system, in addition to any other binaries (for example memtest, refind) you plan to boot via FOG.

    The other likely blocker is the build itself. Naturally, only iPXE can sign binaries that the iPXE Shim will support. Currently the FOG installer actually builds a slightly modified iPXE binary from source. While I’m unsure if these are all that different from the pre-built binaries from 2.0 in terms of support and functionality, it would at the very least need to be changed to instead pull the iPXE 2.0 binaries.

    I don’t think any of these are particularly hard to overcome or deal with though. The bottom line is, 2.0 makes it easier, but only to a point. To get real proper Secure Boot support in FOG, they’ll likely need to generate their own signing keys, and start signing at least the FOS kernels (if not iPXE itself) and update FOG to include shim support somehow.

    That said, for basic support, I doubt they would need to go the full mile and get a Microsoft approved signing key, I think distributing a certificate/key you can enroll via MokManager and using a pre-existing signed shim (like the iPXE provided one) would more than suffice for most usecases. I’m not sure how difficult it would actually be to implement any of this into FOG, that’s a question for someone who knows PHP and is more familiar with the FOG codebase than I.

    Sorry if that’s a bit long winded, it’s not an easy topic to distill. Hope that helps though.

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    J

    @Tom-Elliott Thanks for the clarification! I’ll try upgrading to the latest stable version, I was planning on doing this anyway.

    I’ll look into the Persistent Groups plugin and see how it works!

119

Online

12.7k

Users

17.6k

Topics

156.6k

Posts