![]() Your use of the packages on this site means you understand they are not supported or guaranteed in any way. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.įortunately, distribution rights do not apply for internal use. If you are an organization using Chocolatey, we want your experience to be fully reliable.ĭue to the nature of this publicly offered repository, reliability cannot be guaranteed. Human moderators who give final review and sign off.Security, consistency, and quality checking.ModerationĮvery version of each package undergoes a rigorous moderation process before it goes live that typically includes: when the single binary is built natively for both x86-64 and arm64), but it also has some improvements and bugfixes:Īdded support for parsing some some HP images that use EFI_GUIDED_SECTION_LZMA_HP GUID for their LZMA-compressed sections, thanks to support for "Extract Uncompressed." and "Uncompressed Hex View." actions in UEFITool, both are useful in expecting the raw uncompressed data of compressed items, and will help catch and fix some otherwise invisible issues like #178, thanks to support for proper parsing of ME File Partition Table header version 2.1, improved parsing of the previous versions 1.0 and 2.0, thanks to and CI\CD, updated its configuration to use newer runners, fixed some Coverity warnings found because it's working again, thanks to and Qt 5.6.3 as universal library for macOS, and updated unixbuild.Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community. Support for x86-64 128Kb Recovery Startup AP Data, a special 16 byte entry at a fixed address inside a Padding file in some PEI volumes on x86-64 PCs, thanks to for AMI ROM Hole files, that need to remain at fixed base addresses inside the image, thanks to fixes and small improvements:įix for a crash during ME FPT parsing, thanks to for reporting and for the fixįix for builds on Windows with MinGW, thanks to for reporting and for the fixįix for builds on multiple BSD variants for multiple architectures, thanks to and for C 17 compatibility, thanks to for CMake files to make UEFITool compatible with Qt 6.0/6.1/6.2, thanks to for OSes that call Qt5 qmake not just qmake, but qmake-qt5 (Fedora, FreeBSD), thanks to to make static analysers happier, thanks to to make Kaitai-based parsers do one less memory copy, thanks to and FlatHub app for UEFITool and the files required for it, thanks to first release of 2022 is mostly about testing the new universal binaries for macOS (i.e. It also adds FreeBSD to the list of supported OSes thanks to effort to make the tools buildable there. This release is full of minor improvements and fixes for minor issues that laid unresolved for several years due to them being so minor. ![]() "Extract body" action did not work for some section types. Issues in descriptor and capsule parsing are non-fatal now, thanks to for reporting. UEFIExtract and UEFIFind can again be built with slightly older versions of CMake, thanks to for reporting. Unicode text search is working again, thanks to and for reporting. Universal macOS package for UEFITool is an app bundle again, thanks to and for reporting. Fixes are now in development, will be gradually included in the next updates.Īdded -help (-h) and -version (-v) to UEFIExtract and UEFIFind, this makes them easier to use in scripts. This is another step towards "minimize manual parsing" goal stated by rewriting FIT/ACM/BootGuard parsers in KS, other NVRAM-related parsers will follow in the next updates.Īdded fuzzing targets for libFuzzer-compatible and AFL-compatible fuzzers, which already uncovered a treasure throve of issues. Replaced AMI NVAR parser with KaitaiStruct-based one. A bugfix release, with huge thanks to all the people that reported those new bugs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |