Here's a simple example. c:\windows\system32\drivers\etc\hosts
Have you ever modified that file to get the OS to behave differently, i.e., map a hostname to an ip address that is different from what DNS reports?Code:# Copyright (c) 1993-2006 Microsoft Corp. # # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # # This file contains the mappings of IP addresses to host names. Each # entry should be kept on an individual line. The IP address should # be placed in the first column followed by the corresponding host name. # The IP address and the host name should be separated by at least one # space. # # Additionally, comments (such as these) may be inserted on individual # lines or following the machine name denoted by a '#' symbol. # # For example: # # 102.54.94.97 rhino.acme.com # source server # 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost ::1 localhost
Granted, this is somewhat different than reverse engineering the boot binary in order to unlock some hidden "feature" or is it really? Just because this file's provided in plain text form and contains comments regarding how it should be modified, is no reason the copyright notice at the top is any less valid. By modifying it I have in effect done "reverse engineering" of how the Windows TCP/IP stack works, and by distributing it here I'm probably in violation of the license agreement somehow.
Somewhat different? That is a huge difference. A file provided by the manufacture that is designed to be modified by the user is one thing. The manufacture meant it to be modified. I guess if you want to go down that route any change you make by changing the network card settings to how the files are displayed is technically changing the application in your terms.
And have I modified that file before, NO as I don't do windows.