No edit summary
|
No edit summary
|
||
Line 10: | Line 10: | ||
| developer = |
| developer = |
||
| released = {{Start date and age|1998|05|26}} |
| released = {{Start date and age|1998|05|26}} |
||
| latest release version = 4.2. |
| latest release version = 4.2.2 |
||
| latest release date = {{Start date and age| |
| latest release date = {{Start date and age|2024|01|03}} |
||
| latest preview version = |
| latest preview version = |
||
| latest preview date = |
| latest preview date = |
This article relies excessively on referencestoprimary sources. Please improve this article by adding secondary or tertiary sources.
Find sources: "UPX" – news · newspapers · books · scholar · JSTOR (February 2015) (Learn how and when to remove this message) |
![]() | |
Initial release | May 26, 1998; 26 years ago (1998-05-26) |
---|---|
Stable release | 4.2.2 / January 3, 2024; 6 months ago (2024-01-03) |
Repository | |
Written in | C++, Assembly |
Operating system | Microsoft Windows, Linux, macOS, DOS, Atari TOS |
Platform | i386, MIPS, AMD64, ARM, PowerPC, m68k |
Available in | English |
Type | Executable compression |
License | GPL with exception for compressed executables,[1] proprietary for compression algorithm in binary distributions[2] |
Website | upx |
UPX (Ultimate Packer for Executables) is a free and open source executable packer supporting a number of file formats from different operating systems.[3][4]
UPX uses a data compression algorithm called UCL,[5] which is an open-source implementation of portions of the proprietary NRV (Not Really Vanished)[6] algorithm.[2]
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.[7] 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:
argv[0]
will not be meaningful.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:[8]
UPX does not currently support PE files containing CIL code intended to run on the .NET Framework.
Packers such as Ultimate Packer for Executables (UPX) are more of executable compressors as size reduction is the primary goal, not obfuscation, which can be a byproduct ...
One of the most prolific executable packers is UPX (the Ultimate Packer for executables). Not only does it handle dozens of different executable formats, but also its source code is available online.
upx(1)
– Linux General Commands Manual
Data compression software
| |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Archivers with compression (comparison) |
| ||||||||||||
Non-archiving compressors |
| ||||||||||||
Audio compression (comparison) |
| ||||||||||||
Video compression (comparison) |
| ||||||||||||
|