“Autorun.inf”的意思、由来-开放百科全书

An autorun.inf file is a text file that can be used by the AutoRun and AutoPlay components of Microsoft Windows operating systems. For the file to be discovered and used by these component, it must be located in the root directory of a volume. As Windows has a case-insensitive view of filenames, the autorun.inf file can be stored as AutoRun.inf or Autorun.INF or any other case combination.

The AutoRun component was introduced in Windows 95 as a way of reducing support costs. AutoRun enabled application CD-ROMs to automatically launch a program which could then guide the user through the installation process. By placing settings in an autorun.inf file, manufacturers could decide what actions were taken when their CD-ROM was inserted. The simplest autorun.inf files have just two settings: one specifying an icon to represent the CD in Windows Explorer (or "My Computer") and one specifying which application to run.

Extra settings have been added in successive versions of Windows to support AutoPlay and other new features.

The autorun.inf file

autorun.inf is an ASCII text file located in the root folder of a CD-ROM or other volume device medium (See AutoPlay device types). The structure is that of a classic Windows .ini file, containing information and commands as "key=value" pairs, grouped into sections.^[1] These keys specify:

Abuse

Autorun.inf has been used to execute a malicious program automatically, without the user knowing.^[4]^[5] This functionality was removed in Windows 7 and a patch for Windows XP and Vista was released on August 25, 2009 and included in Microsoft Automatic Updates on February 8, 2011.^[5]^[8]^[9]

Inf handling

The mere existence of an autorun.inf file on a medium does not mean that Windows will automatically read it or use its settings. How an inf file is handled depends on the version of Windows in use, the volume drive type and certain Registry settings.

Assuming Registry settings allow, the following autorun.inf handling takes place:

A simple example

This simple autorun.inf file specifies setup.exe as the application to run when AutoRun is activated. The first icon stored within setup.exe itself will represent the drive in Explorer:

Sections

Following are the sections and keys allowed in a valid autorun.inf.^[3] There also exist architecture specific section types for systems such as Windows NT 4 running on RISC. However these are long outdated and not described here.

[autorun]

The autorun section contains the default AutoRun commands. An autorun.inf file must contain this section to be valid. Keys allowed are:

[Content]

The Content section allows authors to communicate the type and intent of content to AutoPlay without AutoPlay having to examine the media.

Valid keys are: MusicFiles, PictureFiles, VideoFiles. Each key can be set to indicate true or false values and values are not case sensitive.

[ExclusiveContentPaths]

Limits AutoPlay's content search to only those folders listed, and their subfolders. The folder names are always taken as absolute paths (a path from the root directory of the media) whether or not a leading slash is used.

[IgnoreContentPaths]

AutoPlay's content search system will not scan the folders listed, nor their subfolders. IgnoreContentPaths takes precedence over ExclusiveContentPaths so if a path given in a [IgnoreContentPaths] section is a subfolder of a path given in an [ExclusiveContentPaths] section it is still ignored.

[DeviceInstall]

This section is used to indicate where driver files may be located. This prevents a lengthy search through the entire contents of a CD-ROM. Windows XP will fully search:

without this section present. All other media should include this section to have Windows XP autodetect any drivers stored on that media.

The section is not used with AutoRun or AutoPlay and is only referred to during a driver installation phase. The only valid key is:

which lists a path Windows will search for driver files. All subdirectories of that path are also searched. Multiple key entries are allowed.

If no DriverPath entry is provided in the {{mono|[DeviceInstall]}} section or the DriverPath entry has no value, then that drive is skipped during a search for driver files.

References

1. ^¹{{Cite web| url = http://msdn.microsoft.com/en-us/library/cc144206(VS.85).aspx| title = Creating an AutoRun-Enabled Application| publisher = Microsoft| work = MSDN Library}}
2. ^{{Cite web| url = http://support.microsoft.com/kb/136214| title = How to Test autorun.inf Files| publisher = Microsoft| work = Knowledge Base}}
3. ^¹²³⁴{{Cite web| url = http://msdn.microsoft.com/en-us/library/cc144200(VS.85).aspx| title = Autorun.inf Entries| publisher = Microsoft| work = MSDN Library}}
4. ^{{Cite web| url = http://blogs.msdn.com/e7/archive/2009/04/27/improvements-to-autoplay.aspx| title = Improvements to AutoPlay| publisher = Microsoft| work = Engineering Windows 7 blog}}
5. ^{{Cite web| url = http://support.microsoft.com/kb/971029| title = Update to the AutoPlay functionality in Windows| publisher = Microsoft| work = Knowledge Base}}
6. ^¹{{cite web|url=http://www.csoonline.com/article/2131830/malware-cybercrime/security-researchers-discover-link-between-stuxnet-and-flame.html|title=Security researchers discover link between Stuxnet and Flame|first=Lucian|last=Constantin|publisher=}}
7. ^¹²{{cite web|url=http://blogs.technet.com/b/srd/archive/2009/09/11/autoplay-windows-7-behavior-backported.aspx|title=AutoPlay Windows 7 behavior backported|publisher=}}
8. ^¹{{cite web|url=http://www.csoonline.com/article/2132598/malware-cybercrime/security-firms-warn-of-spreading-windows-autorun-malware.html|title=Security firms warn of spreading Windows AutoRun malware|first=Antone|last=Gonsalves|publisher=}}
9. ^¹{{cite web|url=https://www.theregister.co.uk/2011/02/08/microsoft_windows_autorun_retirement|title=Microsoft finally says adios to Autorun|publisher=}}