Time bomb (software)

In computer software, a time bomb is part of a computer program that has been written so that it will start or stop functioning after a predetermined date or time is reached. The term "time bomb" does not refer to a program that stops functioning a specific number of days after it is installed; instead, the term "trialware" applies. Time bombs are commonly used in beta (pre-release) software when the manufacturer of the software does not want the beta version being used after the final release date. One example of time bomb software would be Microsoft's Windows Vista Beta 2, which was programmed to expire on May 31, 2007.[1] The time limits on time bomb software are not usually as heavily enforced as they are on trial software, since time bomb software does not usually implement secure clock functions.

This article is part of a series on
Information security
Related security categories
Threats
Defenses

Comparison of logic bombs and time bombs

The main differences between logic bombs and time bombs is that a logic bomb may have a timing function implemented into it as a failsafe if the conditions are not met in a certain time period (it may delete itself or activate its payload using the timing system), while time bombs only use timing functions to (de)activate themselves. Time bombs, once activated, will unload their payload (which may be malicious) in a similar way logic bombs deliver their payloads to the target. The main difference between both time and logic bombs and fork bombs, is that a fork bomb has no payload per se, and instead does its damage by continually replicating itself to deplete available system resources.

History

The first use of a time bomb in software may have been with the Scribe markup language and word processing system, developed by Brian Reid. Reid sold Scribe to a software company called Unilogic (later renamed Scribe Systems[2]), and agreed to insert a set of time-dependent functions (called "time bombs") that would deactivate freely copied versions of the program after a 90-day expiration date. To avoid deactivation, users paid the software company, which then issued a code that defused the internal time bomb feature.[3]

Richard Stallman saw this as a betrayal of the programmer ethos. Instead of honoring the notion of share-and-share alike, Reid had inserted a way for companies to compel programmers to pay for information access[4] (see Events leading to GNU).

gollark: Much better.
gollark: ++magic py " ".join(map(lambda x: x[1:], """fish: “./a.out” terminated by signal SIGSEGV (Address boundary error)""".split(" ")))
gollark: ++magic py " ".join(map(lambda x: x[1:], "fish: “./a.out” terminated by signal SIGSEGV (Address boundary error)".split(" ")))
gollark: ... why is my malloc implementation not segfaulting?
gollark: * egmentation fault (ore umped)

See also

References
  1. Windows Vista home page
  2. PostScript Printer Driver Optimization Case Study, Adobe Systems, Technical Note #5042, 31 March 1992. Page 5.
  3. Williams, Sam (March 2002). "Free as in Freedom – Richard Stallman's Crusade for Free Software". O'Reilly. Retrieved 2008-09-26. In 1979, Reid made the decision to sell Scribe to a Pittsburgh-area software company called Unilogic. His graduate-student career ending, Reid says he simply was looking for a way to unload the program on a set of developers that would take pains to keep it from slipping into the public domain. To sweeten the deal, Reid also agreed to insert a set of time-dependent functions- "time bombs" in software-programmer parlance-that deactivated freely copied versions of the program after a 90-day expiration date. To avoid deactivation, users paid the software company, which then issued a code that disabled the internal time-bomb feature.
  4. Williams, Sam (March 2002). "Free as in Freedom – Richard Stallman's Crusade for Free Software". O'Reilly. Retrieved 2008-09-26. For Reid, the deal was a win-win. Scribe didn't fall into the public domain, and Unilogic recouped on its investment. For Stallman, it was a betrayal of the programmer ethos, pure and simple. Instead of honoring the notion of share-and-share alike, Reid had inserted a way for companies to compel programmers to pay for information access.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.