1
1
Fork 0
mirror of https://github.com/pbatard/rufus.git synced 2024-08-14 23:57:05 +00:00

[efi] update UEFI:NTFS's NTFS and exFAT drivers to latest

* Now uses read-only NTFS drivers v1.4 from https://github.com/pbatard/ntfs-3g.
* Like previous ones, aa64, ia32 and x64 versions are Secure Boot signed (but not arm).
* Fixes the recent potential vulnerabilities found in https://github.com/tuxera/ntfs-3g.
* Also update exFAT drivers to v1.9 from https://github.com/pbatard/efifs.
This commit is contained in:
Pete Batard 2022-11-16 18:19:32 +00:00
parent 9727fd4342
commit 419522c803
No known key found for this signature in database
GPG key ID: 38E0CF5E69EDD671
4 changed files with 20 additions and 10 deletions

View file

@ -3,18 +3,18 @@ Rufus for NTFS and exFAT UEFI boot support.
See https://github.com/pbatard/uefi-ntfs for more details.
This image, which you can mount as FAT filesystem or open in 7-zip, contains
the following data:
This image, which can be mounted as a FAT file system or opened in 7-zip,
contains the following data:
o Secure Boot signed NTFS UEFI drivers, derived from ntfs-3g [1].
These drivers are the exact same as the read-only binaries from release 1.3,
These drivers are the exact same as the read-only binaries from release 1.4,
except for the addition of Microsoft's Secure Boot signature.
Note that, per Microsoft's current Secure Boot signing policies, the 32-bit
ARM driver (ntfs_arm.efi) is not Secure Boot signed.
o Non Secure Boot signed exFAT UEFI drivers from EfiFs [2].
These drivers are the exact same as the binaries from EfiFs release 1.8 and
because they are licensed under GPLv3, they cannot be Secure Boot signed.
These drivers are the exact same as the binaries from EfiFs release 1.9 but,
because they are licensed under GPLv3, cannot be Secure Boot signed.
o Secure Boot signed UEFI:NTFS bootloader binaries [3].
These drivers are the exact same as the binaries from release 2.2, except for

Binary file not shown.