UPX

UPX uses a data compression algorithm called UCL,{{cite web|author=Markus Oberhumer|title=UCL data compression library|url=https://www.oberhumer.com/opensource/ucl/|website=oberhumer.com|access-date=2022-01-11|archive-date=2024-06-28|archive-url=https://web.archive.org/web/20240628163818/https://www.oberhumer.com/opensource/ucl/|url-status=live}} which is an open-source implementation of portions of the proprietary NRV (Not Really Vanished){{cite web|author=Markus Oberhumer|title=NRV Compression Library|url=https://www.oberhumer.com/products/nrv/|archive-url=https://archive.today/20120909151357/http://www.oberhumer.com/products/nrv/|archive-date=September 9, 2012}} algorithm.{{cite web|title=The UPX Hacker's Guide|url=https://github.com/upx/upx/blob/master/README.SRC|website=GitHub|date=19 February 2022|access-date=14 September 2016|archive-date=14 May 2022|archive-url=https://web.archive.org/web/20220514090514/https://github.com/upx/upx/blob/master/README.SRC|url-status=live}}

UCL has been designed to be simple enough that a decompressor can be implemented in just a few hundred bytes of code. UCL requires no additional memory to be allocated for decompression, a considerable advantage that means that a UPX packed executable usually requires no additional memory.

UPX (since 2.90 beta) can use LZMA on most platforms; however, this is disabled by default for 16-bit due to slow decompression speed on older computers (use --lzma to force it on).

Starting with version 3.91, UPX also supports 64-Bit (x64) PE files on the Windows platform.{{Cite web |url=https://upx.github.io/upx-news.txt |title=UPX News |access-date=2016-09-14 |archive-date=2018-01-04 |archive-url=https://web.archive.org/web/20180104064454/https://upx.github.io/upx-news.txt |url-status=live }} This feature is currently declared as experimental.

UPX supports two mechanisms for decompression: an in-place technique and extraction to temporary file.

The in-place technique, which decompresses the executable into memory, is not possible on all supported platforms. It has the advantage of being more efficient in terms of memory, and that the environment set up by the OS remains correct.

The rest uses extraction to temporary file. This procedure involves additional overhead and other disadvantages; however, it allows any executable file format to be packed. The extraction to temporary file method has several disadvantages:

• Special permissions are ignored, such as suid.
• argv[0] will not be meaningful.
• Multiple running instances of the executable are unable to share common segments.

Unmodified UPX packing is often detected and unpacked by antivirus software scanners. UPX also has a built-in feature for unpacking unmodified executables packed with itself.

UPX supports the following formats:{{man|1|upx|ManKier}}

• Portable Executable (PE, EXE and DLL files):
• ARM (Windows CE)
• 32-bit x86 (Windows Desktop)
• 64-bit x86-64 (Windows Desktop, still experimental)
• RTM32 (DOS extender, as generated by Borland C/Pascal compilers){{Cite web|url=https://www.vogons.org/viewtopic.php?t=25997|title=dos extender rtm32 - fileformat of the stub? \ VOGONS|access-date=2022-01-11|archive-date=2022-01-11|archive-url=https://web.archive.org/web/20220111150647/https://www.vogons.org/viewtopic.php?t=25997|url-status=live}}
• COFF executables, used by DJGPP2
• a.out format, BSD i386 (removed)
• Raw 8086/DOS files:
• DOS/COM (including some binary images)
• DOS/EXE
• DOS/SYS
• Watcom/LE (used by DOS4G, PMODE/W, DOS32A and CauseWay){{Citation needed|date=November 2022}}
• TMT/adam (as generated by the TMT Pascal compiler)
• Atari/TOS
• Linux kernel, i386, x86-64 and ARM
• Linux Executable and Linkable Format, i386, x86-64, ARM, PowerPC, MIPS
• PlayStation 1/EXE (MIPS R3000)
• Darwin Mach-O, ppc32, i386, and x86-64

UPX does not currently support PE files containing CIL code intended to run on the .NET Framework.

{{Reflist|group="nb"|refs=

The facility to compress DOS .COM-style files can be utilized also to compress other binary executable files. Some FreeDOS and EDR-DOS kernel files are known to be UPX-compressible this way.

The facility to compress DOS .COM-style files can be utilized also to compress non-executable binary data files, if the driver/application using these files has been enhanced to detect UPX-compressed files and jump to the decompressor embedded in the file. FreeDOS is known to utilize this for .CPX files, UPX-compressed .CPI font files.

For the DOS targets, UPX supports a special option -8086 in order to force the embedded decompressor to become compatible with 8088/8086 processors, so that the compressed files can be executed and decompressed even on the earliest PCs running DOS.

}}

{{reflist}}

{{Portal|Free and open-source software}}

• {{Official website}}

{{compression software implementations}}

Category:Free data compression software

Category:Free software programmed in C++

Category:EXE packers

Category:1998 software

Category:Assembly language software