Universal Filesystem Driver Pre-Boot Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current pre-boot environments of information handling systems face difficulties in accessing storage devices, lack universal filesystem drivers, and inadequate authentication for cloud-based booting, particularly in handling different filesystem types and sizes, and securing downloads.

Innovation Solution

A universal filesystem driver is downloaded and loaded in the pre-boot environment from a back-end server, acting as a single pre-boot firmware volume with drivers for multiple filesystems, and includes secure authentication mechanisms using metadata formats like SUFI and SEGI for verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple filesystem drivers are embedded in the pre-boot environment, then different filesystem types and sizes can be handled, but the device complexity and memory requirements increase

Engineering Contradiction:
Improvefilesystem compatibilityVSAvoiddriver complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal filesystem driver that can handle multiple filesystem types (FAT, NTFS, EXT, etc.) through a unified interface and common codebase. This single driver provides multi-functionality by detecting the filesystem type and applying appropriate handling routines, eliminating the need for separate dedicated drivers for each filesystem format.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The universal driver acts as an intermediary layer between the pre-boot environment and various filesystem types. It provides a standardized interface that the pre-boot environment interacts with, while the driver internally manages the diversity of filesystem protocols and formats, shielding the upper layers from complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If authentication is performed at the disk image level only, then the authentication process is simple, but individual files within the image cannot be verified securely

Engineering Contradiction:
Improveauthentication granularityVSAvoidauthentication mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication mechanism is segmented into two levels: disk image-level authentication using digital signatures on the entire image, and file-level authentication using metadata structures (SUF/SEGI) that contain individual file hashes and signatures. This segmentation allows verification at appropriate granularities without requiring complex mechanisms at both levels simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Authentication metadata (SUF/SEGI structures containing file hashes and digital signatures) is prepared in advance during the disk image creation process. This preliminary action enables rapid verification during boot without requiring complex real-time authentication computations, as the verification data is already computed and embedded.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If a universal filesystem driver is downloaded from a remote server, then the latest drivers and security updates are obtained, but network dependency and download time are introduced

Engineering Contradiction:
Improvedriver securityVSAvoidboot time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The universal filesystem driver and its authentication metadata are downloaded and verified during the pre-boot phase before the operating system loads. This preliminary action ensures security updates are applied before system use, and the driver is cached for subsequent boots, minimizing impact on normal boot times.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements verification feedback mechanisms where the downloaded driver and metadata are authenticated using digital signatures and hashes before being installed. This feedback loop ensures security without requiring re-downloads, as verification failures would prevent installation rather than extend operational boot time.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11500995B1Secure boot runtime universal filesystem
Publication Date: 2022.11.15 DELL PROD LP
  • US11500995B1 patent drawing
  • US11500995B1 patent drawing
  • US11500995B1 patent drawing

AI summary

An information handling system may include at least one processor; and a computer-readable medium having instructions thereon that are executable by the at least one processor for: prior to initialization of an operating system, executing a pre-boot environment; and within the pre-boot environment, downloading a universal filesystem driver from a first back-end server and loading the universal filesystem driver in the pre-boot environment, wherein the universal filesystem driver is a single pre-boot firmware volume that comprises drivers for a plurality of different filesystems.