A self-extracting archive (SFX or SEA) is a computerexecutable program which combines compressed data in an archive file with machine-executable code to extract the information. Run on a compatible operating system, there is no need for a suitable extractor in the target computer to extract the data. The executable part of the file is known as a decompressor stub.
Self-extracting files are used to share compressed files with a party that may not have the software needed to decompress a regular archive. Users can also use self-extracting archives to distribute their own software. For example, the WinRAR installation program is made using the graphical GUI RAR self-extracting module Default.sfx.
Overview
Self-extracting archives contains an executable file module, a module used to run uncompressed files from compressed files. Such a compressed file does not require an external program to decompress the contents of the self-extracting file, and can run the operation itself. However, file archivers like WinRAR can still treat a self-extracting file as though it is any other type of compressed file. By using a file archiver, users can view or decompress self-extracting files they received without running executable code (for example, if they are concerned about viruses).
A self-extracting archive is extracted and stored on a disk when executed under an operating system that supports it. Many embedded self-extractors support a number of command line arguments, such as specifying the target location or selecting only specific files.
Unlike self-extracting archives, non-self-extracting archives only contain archived files and must be extracted with a program that is compatible with them. While self-extracting archives cannot be extracted under another operating system, they can usually still be opened using a suitable extractor as this tool will disregard the executable part of the file and extract only the archive resource. The self-extracting executable may need to be renamed to contain a file extension associated with the corresponding packer; archive file formats known to support this include ARJ[1] and ZIP.[2][3] Typically, self-extracting files have a .exe extension, just like any other executable file.
For example, an archive may be called somefiles.zip—it can be opened under any operating system by a suitable archive manager which supports both the file format and compression algorithm used.[2] It may also be converted into somefiles.exe, which will self-extract under Microsoft Windows. It will not self-extract under Linux, but can be opened with a suitable archive manager. Files that are not recognized as archives by archive managers due to their executable extension can be renamed into .zip.[3] This works for ZIP archives due to the way the ZIP header is defined, but not necessarily for other less flexible archive format.
There are several functionally equivalent but incompatible archive file formats, including ZIP, RAR, 7z and many others. Many programs can handle multiple types of archives, whereas others can create, extract, or modify only one type. Additionally, there is a distinction between the file format and the compression algorithm. A single file format, such as 7z, can support multiple different compression algorithms including LZMA, LZMA2, PPMd and BZip2. Decompression utilities must be able to handle both the file format and the algorithm used when expanding self-extracting or standard archives. Depending on the options used to create a self-extracting archive, the executable code placed at the beginning may vary. If you compare a LZMA 7z archive to a LZMA2 7z archive, for example, the decompression routines will differ
Several programs can create self-extracting archives. Among the Windows archivers are WinZip, WinRAR, 7-Zip, WinUHA, KGB Archiver, Make SFX, the built-in IExpress wizard and many others, some experimental. Macintosh users may choose StuffIt, The Unarchiver, or 7z X as their archivers. There are also programs that create self-extracting archives on Unix as shell scripts, which utilize programs like tar and gzip (which must be present in the destination system). Others (like 7-Zip or RAR) can create self-extracting archives as regular executables in ELF format. One of the early examples of self-extracting archives is the Unix shar archive, which combined a number of text files into a shell script that recreated their original content after being executed.
It is possible to archive both data and executable files with self-extracting archives. They must be distinguished from executable compression, where the executable file only contains a single executable, and running the file does not result in the uncompressed file being stored on disk, but in its code being executed in memory after decompression.
Advantages
Archiving files rather than sending them separately allows several related files to be combined into a single resource. Another benefit is that it reduces the size of files that aren't already efficiently compressed (most compression algorithms cannot reduce the size of already compressed files. Compression usually reduces the size of plain text documents, but rarely affects JPEGs or word processor documents, as many modern word processors already involve a certain level of compression). In addition to the benefits of compressed archives, self-extracting archives can also be used by users without the necessary programs for extracting their contents, as long as they run a compatible operating system. A self-extracting archive may still be more convenient for users who do have archive management software.
As long as the underlying compression algorithm and format allow it, self-extracting archives can also be encrypted for security. It is important to note, however, that in many cases, the file and directory names are not included in the encryption and can be viewed by anyone without a key or password. If a person can guess part of the contents of the files from their names or context alone, an attacker may be able to break the encryption on the entire archive with only a reasonable amount of computing power and time. A more appropriate encryption algorithm should be used for important files.
Disadvantages
A disadvantage of self-extracting archives is that running executables of unverified reliability, for example when sent as an email attachment or downloaded from the Internet, may be a security risk.[2] An executable file described as a self-extracting archive may actually be a malicious program.[2] One protection against this is to open it with an archive manager instead of executing it (losing the advantage of self-extraction); the archive manager will either report the file as not an archive or will show the underlying metadata of the executable file - a strong indication that the file is not actually a self-extracting archive.
Additionally, some systems for distributing files do not accept executable files in order to prevent the transmission of malicious programs. These systems disallow self-extracting archive files unless they are cumbersomely renamed by the sender to, say, somefiles.exe, and later renamed back again by the recipient. This technique is gradually becoming less effective, however, as an increasing number of security suites and antivirus software packages instead scan file headers for the underlying format rather than relying on a correct file extension. These security systems will not be fooled by an incorrect file extension, and are particularly prevalent in the analysis of email attachments.
Self-extracting archives will only run under the operating system family and platform with which they are compatible, making it more difficult to extract their contents under other systems.[2] Examples of self-extracting archives, which can be run on multiple targets (such as DOS and CP/M) rather than only the archive contents to be usable under multiple systems, are very rare, because they require the embedded decompressor stub to be a fat binary.[4][5][6][7]
Also, since the self-extracting archives must include executable code to handle the extraction of the contained archive file, they are slightly larger than the original archive.
^Paul, Matthias R. (1997-07-30) [1994-05-01]. "Chapter I.2. Novell DOS 7 Updates: iii. Entpacken der Updates". NWDOS-TIPs — Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds. MPDOSTIP (in German) (3 ed.). Archived from the original on 2017-09-10. Retrieved 2014-08-06. Möchten Sie mit ARJ arbeiten, können Sie die .EXE-Datei auch einfach zu .ARJ umbenennen. ARJ kann darin enthaltene Dateien mit den üblichen Optionen entpacken (innerhalb des Norton Commanders ist dies allerdings wegen des anderen Dateikopfes nicht möglich). (NB. NWDOSTIP.TXT is a comprehensive work on Novell DOS 7 and OpenDOS 7.01, including the description of many undocumented features and internals. It is part of the author's yet larger MPDOSTIP.ZIP collection maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the NWDOSTIP.TXT file.) [1]
^ abcdePaul, Matthias R. (2010-12-03). "Firmware 2.00 für Sony Alpha DSLR-A850/DSLR-A900". Mi-Fo (in German). Archived from the original on 2015-10-03. Retrieved 2022-05-28. […] bei modernen Systemen ist die Funktionalität, in ZIP-Archive hineinzugehen, als wären es Unterverzeichnisse im Dateisystem, voll in die Shell integriert, so daß man dafür gar kein eigenständiges Entpackprogramm mehr bemühen muß, wie das früher der Fall war. Das funktioniert auch unter Windows (Explorer) schon seit fünfzehn Jahren so (Windows 95), und selbst unter DOS läßt sich sowas problemlos für die Kommandozeile einrichten, bzw. war in Dateimanagern wie dem Norton Commander schon vor bald zwanzig Jahren integriert. […] Es ist eine wirklich sehr schlechte Idee, ausführbare Dateien (wie .EXE-Dateien) über das Netz verteilen zu wollen - im Grunde halte ich das für unverantwortlich, gerade wenn man auch unbedarfte "Nur-Anwender" in der Zielgruppe hat. Ausführbare Dateien stellen ein erhebliches Sicherheitsrisiko dar, denn sie können Viren enthalten (und tun dies auch oft). Deshalb blockieren viele Virenscanner und Firewalls sowas, und die Anwender, die sich an die Instruktionen auf Sonys Webseite halten (gerade, weil sie nichts falsch machen möchten), werden Schwierigkeiten haben, die Datei überhaupt herunterladen zu können. Die Leute, die es dennoch schaffen, werden u.U. mit dem nächsten Problem konfrontiert, nämlich der Tatsache, daß der spezielle Selbstentpacker, der in der .EXE-Datei integriert ist, nur unter bestimmten Versionen von Windows funktioniert. Manche Windows x64-Versionen, manche Windows Starter-Versionen und manche älteren Windows-Versionen werden nicht unterstützt. Das muß nicht so sein, man müßte einfach nur einen Selbstentpacker verwenden, der mit allen Windows-Versionen kompatibel ist. […][2]
^Elliott, John C. (1997-01-18) [1997-01-11]. "PMSFX 2". Newsgroup: comp.os.cpm. Archived from the original on 2021-12-13. Retrieved 2021-12-13. […] I've written a version of PMSFX that produces .COM files unpackable under DOS and CP/M (the first three bytes are both legal Z80 code, legal 8086 code and legal PMA header). You can find it […] as a self-extracting archive. […]
^Elliott, John C. (2012-06-20) [2005-01-05]. "Generic CP/M". Seasip.info. Archived from the original on 2021-11-17. Retrieved 2021-12-12. […] Self-extracting archives are .COM files containing a number of smaller files. When you run one, it will create its smaller files […] The self-extract archive programs will run under DOS (2 or later) or CP/M, with identical effects. To extract them under Unix, you can use ZXCC […] PMSFX21X.COM […] PMSFX is the program that was used to generate these self-unpacking archives. This version (2.11) can generate archives which unpack themselves under CP/M or DOS. You will need PMARC to use PMSFX. […]((cite web)): External link in |quote= (help)[3]
^Elliott, John C. (2009-10-27). "CP/M info program". Newsgroup: comp.os.cpm. Archived from the original on 2021-12-13. Retrieved 2021-12-13. […] More fun can be had with self-extract PMArc archives. Start one with […] defb 0EBh, 018h, '-pms-' […] and it's treated as a valid archive by the PMA utilities, sends 8086 processors to 011Ah, and Z80 processors to 0130h. […]
