Skip to content

Releases: SabreTools/BinaryObjectScanner

BurnOutSharp 2.1.0

18 Apr 05:09
Compare
Choose a tag to compare

This is a minor update to the 2.0.* releases:

  • Add AutoPlay Media Studio installer detection and update Setup Factory
  • Move more things to PortableExecutable for better performance and stability
  • Fix over-matching SafeLock check
  • Upgrade to VS2022 solution and AppVeyor
  • Convert library to .NET Standard 2.0
  • Add .NET 6.0 as build target for test executable
  • Update UnshieldSharp and WiseUnpacker to newest versions

BurnOutSharp 2.0.0

28 Mar 03:51
Compare
Choose a tag to compare

This is a major overhaul and a breaking change compared to the 1.x releases:

  • Removal of known over-matching checks
  • Locking of full file scans behind the debug flag
  • Move to stream-based internals
  • Many new checks and a few new protections and packers
  • Increased accuracy and speed

For those using the test executable, you may notice some changes:

  • New flags have been added to allow for more granular scanning of input files and folders
  • Drag and drop functionality still works, but debug is not enabled by default anymore

BurnOutSharp 1.8.0

22 Sep 18:13
Compare
Choose a tag to compare

This is a major overhaul and breaking change compared to the 1.7.x releases:

  • IncludePosition flag has been renamed to IncludeDebug for future expandability
  • Added a few new protection and packer checks
  • Removed EVORE helper class (which attempted to run some executables in very specific circumstances)
  • Updated, fixed, and implemented PE and NE executable reading (only a few gaps missing)
  • Converted the vast majority of content checks to use the new PE and NE reads instead
  • Reduced the surface area of the majority of content checks - reduced possible false positives
  • Validated as many checks as possible locally instead of relying purely on community feedback

For those using the test executable, you may notice some changes:

  • Not all protections will show positions (or the position within the file may seem incorrect) when the IncludeDebug flag is set to true. This is because, where possible, checks have been reduced to more concrete locations and executable sections, therefore making the found position mostly obsolete
  • If an uncaught exception occurs, more information will be printed out to the textfile. This was an oversight on my part originally.

BurnOutSharp 1.7.0

22 Jul 17:56
Compare
Choose a tag to compare

This is a major overhaul compared to the 1.6.x releases:

  • Major improvements to some existing detections, especially packers
  • Additions of a couple of packers
  • Support for InstallShield V3 (Z) Archives
  • Major bugfix and performance fix around scanning files of varying sizes in the same directory

This is a partially breaking release due to the addition of new parallel scanning

BurnOutSharp 1.6.1

14 Apr 16:16
Compare
Choose a tag to compare

This is a bugfix release that removes a bit of problematic code in Valve unpacking that could cause crashes for archives that overmatch.

BurnOutSharp 1.6.0

09 Apr 16:45
Compare
Choose a tag to compare

This is a breaking change! Existing uses of BurnOutSharp, especially if individual scanners are being used, may break with this update. Please check after updating.

  • Fix Wise scanning to follow archive and packer flags
  • Remove Cucko scanning as it over-matches
  • Add internal interfaces for easier development
  • Add some new detections (a lot thanks to @SilasLaspada)
  • Create new helper classes for easier scanning
  • Update WiseUnpacker and UnshieldSharp to newest versions
  • Remove .NET Framework 4.7.2 support
  • Use submodules for external code instead of code mirrors or nuget packages

Please note that no protection should be limited by being on a newer version of .NET anymore due to the submoduled code being built alongside all other code.

BurnOutSharp 1.5.1

22 Jan 19:33
Compare
Choose a tag to compare
  • Add VSCode files for future development
  • Reorganize former "EVORE" code and add notes for future research
  • Fix MPQ archive extraction and scanning
  • Add .NET 5.0 targeting support (limited similarly to .NET Core 3.1 builds from 1.5.0)

BurnOutSharp 1.5.0

04 Nov 05:27
Compare
Choose a tag to compare

Unlike previous releases, this is broken down into sections due to the large number of changes:

Overall Changes:

  • [BREAKING CHANGE] Removed static ProtectionFind.cs and replaced with Scanner.cs class
  • Added MSI extraction for scanning
  • Ensured mspack.dll exists in the builds folder for the MS-CAB extraction library
  • Fixed path outputs for files within archives or archive-like formats. This will more clearly show where a file is from, especially multiple-nesting scenarios.
  • Gated MSI and MS-CAB extraction away from .NET Core 3.1 builds due to incompatibilities with the used libraries. This should allow for .NET Core 3.1 programs to use 90% of the functionality instead of the potentially 0% before.
  • Large bits of code refactoring to better accommodate potential flags around scan types
  • Updated to UnshieldSharp 1.4.2.4

Protection Updates:

  • Modified CD Check checks to be more accurate and remove ones that lead to false positives
  • Added XCP content checks
  • Added UPX packer detection
  • Updated Cactus Data Shield content checks
  • Added and sorted EA-related protection checks
  • Added SolidShield wrapper check
  • Added 321Studios activator content checks
  • Added INTENIUM Trial & Buy content checks
  • Fixed 3PLock over-detection
  • Added MediaMax CD-3 content checks

BurnOutSharp 1.4.1

01 Oct 06:27
Compare
Choose a tag to compare
  • Updated to WiseUnpacker 1.0.1
  • Updated to SharpCompress 0.26.0
  • Fixed automatic packing of additional DLLs
  • Fixed building Test executable

BurnOutSharp 1.4.0

11 Sep 05:36
Compare
Choose a tag to compare
  • Added more archive types to scan internally
  • Added ability to log location of copy protection within a file
  • Simplified most of the code and reorganized
  • Now supports .NET 4.7.2, .NET 4.8, and .NET Core 3.1
  • Fixed issue with LibCrypt