Top Qs
Timeline
Chat
Perspective
Software update
Process of changing installed software to be more modern From Wikipedia, the free encyclopedia
Remove ads
Software update is the process of changing installed software with the intent to make it more modern. It also refers to the stored data used to update software. When storage was significantly more expensive, patching files was the dominant form of update. With the advent of larger distribution storage media and higher Internet bandwidth, it became common to replace entire files instead of patching.
An update may require prior application of other updates, or may require prior or concurrent updates to multiple components. To facilitate updates, operating systems often provide automatic or semi-automatic updating facilities. Package management systems offer update automation.
An update can be any size. An update can be relatively large when the changes add or replace data such as graphics and sound files; for example for a game update. An update usually takes less time to run than an initial installation of the software.
Although often intended to upgrade, an update may instead degrade. An update may include unintentional regression problems. In some cases, an update intentionally disables functionality, for instance, by removing aspects for which the consumer is no longer licensed.
Remove ads
Management
Summarize
Perspective
Software update systems allow for updates to be managed by users and software developers. In the 2017 Petya cyberpandemic, the financial software "MeDoc"'s update system is said to have been compromised to spread malware via its updates.[1][2] On the Tor Blog, cybersecurity expert Mike Perry states that deterministic, distributed builds are likely the only way to defend against malware that attacks the software development and build processes to infect millions of machines in a single, officially signed, instantaneous update.[3] Update managers also allow for security updates to be applied quickly and widely. Update managers of Linux such as Synaptic allow users to update all software installed on their machine. Applications like Synaptic use cryptographic checksums to verify source/local files before they are applied to ensure fidelity against malware.[4][5]
Automatic updating has become more widespread over time. Some cite a cause of its prevalence to be due to Windows support in early 2000s. Service Pack 2 of Windows XP (available in 2004) enabled it by default.
Remove ads
Classification
Summarize
Perspective
Updates are classified many ways. Notable classifications in alphabetical order follow.
Hotfix
A hotfix is a software update that is released outside the normal update cycle or intended to be applied to a live system; often to fix a bug.[6]
Originally, hotfix referred to patching a hot system – a production server that is actively serving clients. For development, such a change usually must be designed quickly and outside normal development processes; at relatively high cost and disrupting other development effort. For the user, a hotfix is relatively risky since it is applied to a server without time for testing it. The risk of applying the hotfix must be weighed against the risk of not applying it. The problem to be fixed might be so critical that inaction is riskier than the potential loss of service.
Over time, the meaning has shifted to an update that is created with urgency or released outside the normal update cycle for the software.
Applying (installing) a hotfix generally involves the same process as any software update. Most modern operating systems and desktop applications can download and apply updates automatically. Network administrators may use software programs to automate and simplify applying updates to the machines they manage.Malicious update
Some hacker may compromise legitimate software update channel and inject malicious code.[7]
Patch
A patch is data for modifying an existing software resource such as a program or a file, often to fix bugs and security vulnerabilities.[8][9] Patch is also the process of applying the data to the existing resource. Patching a system involves applying a patch. A patch may be created to improve functionality, usability, or performance. A patch may be created manually, but commonly it is created via a tool that compares two versions of the resource and generates data that can be used to transform one to the other.
Typically, a patch needs to be applied to the specific version of the resource it is intended to modify, although there are exceptions. Some patching tools can detect the version of the existing resource and apply the appropriate patch, even if it supports multiple versions. As more patches are released, their cumulative size can grow significantly, sometimes exceeding the size of the resource itself. To manage this, the number of supported versions may be limited, or a complete copy of the resource might be provided instead.
Patching allows for modifying a binary executable. Although this can be technically challenging (requires a thorough understanding of the workings of the executable), it may be feasible when the source code is unavailable to build a full executable, and it allows for a smaller distribution which can be more economical than distributing full files.
Although often intended to fix problems, a patch can introduce new problems. In some cases, an update intentionally disables functionality, for instance, by removing aspects for which the consumer is no longer licensed. Patch management is a part of lifecycle management, and involves a strategy and planning of what patches should be applied to which systems and at what times. Typically, a patch is applied in a permanent way (i.e. to storage), but in some cases, a patch is applied to memory (i.e. via a tool such as a debugger) in which case the change is lost when the resource is reloaded from storage.
Software update is sometimes conflated with patch even though they are not synonyms. An update can be implemented using patch files and the patching process. Also, some may contend that patching is not limited to modifying file content; that adding, removing and replacing whole files is patching. Typically, patch connotates a relatively small change, so a patch that is large in size or scope may be called the more general software update or another more specific name such as service pack. Windows NT and its successors (including Windows 2000, Windows XP, Windows Vista and Windows 7) use service pack.[10] Historically, IBM used the terms FixPak and Corrective Service Diskette for such updates.[11]Patch release
Program temporary fix
In IBM terminology, a program temporary fix or product temporary fix (PTF), sometimes depending on date,[12][13] is a one or more bug fixes – distributed in a form ready to install.
A PTF normally follows an Authorized Program Analysis Report (APAR)[14], and where an "APAR fix" was issued, the PTF "is a tested APAR"[15] or set of APAR fixes. However, if an APAR is resolved as "Fixed If Next" or "Permanent Restriction" then there may be no PTF fixing it, only a subsequent release.Security patch
A security patch is a change to correct the weakness described by a vulnerability. The corrective action prevents successful exploitation and removes or mitigates a threat's capability to exploit a specific vulnerability. Patch management is a part of vulnerability management – the cyclical practice of identifying, classifying, remediating, and mitigating vulnerabilities.
Security patches are the primary method of fixing security vulnerabilities in software. Currently Microsoft releases its security patches once a month ("patch Tuesday"), and other operating systems and software projects have security teams dedicated to releasing the most reliable software patches as soon after a vulnerability announcement as possible. Security patches are closely tied to responsible disclosure.
These security patches are critical to ensure that business process does not get affected. In 2017, companies were struck by a ransomware called WannaCry which encrypts files in certain versions of Microsoft Windows and demands a ransom via BitCoin. In response to this, Microsoft released a patch which stops the ransomware from running.
Service pack
In computing, a service pack comprises a collection of updates, fixes, or enhancements to a software program delivered in the form of a single installable package. Companies often release a service pack when the number of individual patches to a given program reaches a certain (arbitrary) limit, or the software release has shown to be stabilized with a limited number of remaining issues based on users' feedback and bug reports. In large software applications such as office suites, operating systems, database software, or network management, it is not uncommon to have a service pack issued within the first year or two of a product's release. Installing a service pack is easier and less error-prone than installing many individual patches, even more so when updating multiple computers over a network, where service packs are common.
Service packs are usually numbered, and thus shortly referred to as SP1, SP2, SP3 etc.[16] They may also bring, besides bug fixes,[17] entirely new features, as is the case of SP2 of Windows XP (e.g. Windows Security Center), or SP3 and SP4 of the heavily database dependent Trainz 2009: World Builder Edition.[18]Unofficial patch
An unofficial patch, a.k.a. community patch and fan patch, is a software update created by a third party, such as a user community, without the involvement of whoever is considered the official maintainer of the software (i.e. original developer). An unofficial patch generally does not change the intended use of the software, in contrast to other third-party adaptions such as mods or cracks.
An unofficial patch is typically intended to repair bugs and provide new capabilities such as support for newer operating systems, increased display resolutions and new display formats.[19][20] While unofficial patches are most common for the PC platform, they can also be found for console games e.g. in context of the emulation community.[21]
A fan translation is an unofficial patch that adds natural language support to software.[22] Fan translations are most common for Japanese role-playing games which are often not localized for Western markets.[23][24]
A slipstream like patch combines multiple official patches into one unofficial update package as a convenience to users when individual patches are only available online or as small incremental updates.
A common motivation for creating an unofficial patch is lack of technical support from the official maintainer which may result from:
- The software reached the maintainer's defined end-of-life[25]
- The software was superseded by a successor product[26]
- The software was originally designed to operate in a substantially different environment and may require improvement/optimization
- The maintainer went out of business[27]
- Support is not economically viable (e.g. localization for small markets)
- A fast solution for a time critical problem (e.g. security holes) when an official one takes too long[28][29][30]
- The official maintainer is unable to cope with the problems[31]
Video game patch
A video game receives an update (often called a patch) to fix problems and to change features such as change game rules and algorithms. These updates may be prompted by the discovery of exploits in the multiplayer game experience that can be used to gain unfair advantages over other players. Extra features and gameplay tweaks can often be added. These kinds of updates are common in first-person shooters with multiplayer capability, and in MMORPGs, which are typically very complex with large amounts of content, almost always rely heavily on updates following the initial release, where updates sometimes add new content and abilities available to players. Because the balance and fairness for all players of an MMORPG can be severely corrupted within a short amount of time by an exploit, servers of an MMORPG are sometimes taken down with short notice to apply a critical fix.
Companies sometimes release games knowing that they have bugs. Computer Gaming World's Scorpia in 1994 denounced "companies—too numerous to mention—who release shoddy product knowing they can get by with patches and upgrades, and who make 'pay-testers of their customers".[32]
Remove ads
Process
Summarize
Perspective
Software update processes vary dramatically. Some notable processes are described here.
Firmware update
Updating firmware (i.e. motherboard BIOS) can be challenging when it involves replacing the entire image on the hardware. As such, an error or interruption during the update process, such as loss of power, may render the hardware unusable.
An update, a binary image, is often installed via a supplier-provided program that overwrite the existing image with another. This program may safeguard against serious damage. For example, the update procedure could make and keep a backup of the firmware in case it determines that the primary copy is corrupt (i.e. via a checksum).
Limited release
In the cases of large updates or of significant changes, distributors often limit availability of updates to qualified developers as a beta test.
Hot patching
Hot patching, also known as live patching or dynamic software updating, is the application of patches without shutting down and restarting the system or the program concerned. This addresses problems related to unavailability of service provided by the system or the program.[33] Method can be used to update Linux kernel without stopping the system.[34][35] A patch that can be applied in this way is called a hot patch or a live patch. This is becoming a common practice in the mobile app space.[36] Companies like Rollout.io use method swizzling to deliver hot patches to the iOS ecosystem.[37] Another method for hot-patching iOS apps is JSPatch.[38]
Cloud providers often use hot patching to avoid downtime for customers when updating underlying infrastructure.[39]
Slipstreaming
Slipstreaming is the act of integrating updates into the installation files of their original app, so that the result allows a direct installation of the updated app.[40][41]
The nature of slipstreaming means that it involves an initial outlay of time and work, but can save a lot of time (and, by extension, money) in the long term. This is especially significant for administrators that are tasked with managing a large number of computers, where typical practice for installing an operating system on each computer would be to use the original media and then update each computer after the installation was complete. This would take a lot more time than starting with a more up-to-date (slipstreamed) source, and needing to download and install the few updates not included in the slipstreamed source.
However, not all updates can be applied in this fashion and one disadvantage is that if it is discovered that a certain update is responsible for later problems, that update cannot be removed without using an original, non-slipstreamed installation source.
Remove ads
See also
- Automatic bug fixing – Automatic repair of software bugs
- Backporting – Developing an update for older software based on an update to a newer version
- Delta encoding – Type of data transmission method
- Dribbleware
- Patch (Unix) – Command for applying changes to text files
- Porting – Process of adapting software to run a different context
- Software maintenance – Modification of software after delivery
- Software release life cycle – Stages in creation of computer software
- SMP/E – Software management utility for mainframes
- Upgrade – Process of improving something by replacing part of it or adding additional parts
- Vulnerability database – Computer security vulnerabilities
- White hat (computer security) – Computer hacker who hacks ethically
Remove ads
References
Wikiwand - on
Seamless Wikipedia browsing. On steroids.
Remove ads