

Those associations are maintained differently from OS to OS, but at their core they associate a particular identifier about a file type such as an extension (Windows) or a media type (browsers), and a program assigned to open it by default.

#.zip creator for mac archive#
Some mappings do exists across the various systems as well.įor example, a ZIP archive would be identified as follows: Linux systems use a mix of extensions and media types, with some auto-detection / “sniffing” of media types based on file content. However, on the Internet (in browsers and email clients) instead of filenames, MIME media types are used with a registry maintained by IANA on behalf of the IETF. On macOS metadata about the file maybe available separately and either a creator code, a type code or a Uniform Type Identifier is used. On Microsoft Windows, files are identified by their extensions, which appears after the “.” in the filename. This was originally discovered in macOS v10.11 (El Capitan) and v10.12 (Sierra), but the latest version of macOS v10.13 (High Sierra) was not tested.

Most anti-virus vendors for macOS are not affected by this issue. The vendor (Apple) does not consider this to be a security issue. This can be used to fool users and antivirus software that relies on file extensions by packaging malicious code inside compressed files with different extensions. Compressed files on macOS are autodetected by the operating system even if they are renamed to certain other extensions.
