Proprietary software

From Infogalactic: the planetary knowledge core
(Redirected from Closed source software)
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found. Proprietary software is computer software for which the software's publisher or another person retains intellectual property rights—usually copyright of the source code, but sometimes patent rights.

Software becoming proprietary

Until the late 1960s computers—large and expensive mainframe computers machines in specially air-conditioned computer rooms—were leased to customers rather than sold.[1][2] Service and all software available were usually supplied by manufacturers without separate charge until 1969.[citation needed] Computer vendors usually provided the source code for installed software to customers.[citation needed][citation needed] Customers who developed software often made it available to others without charge.[citation needed]

In 1969, IBM, which had antitrust lawsuits pending against it, led an industry change by starting to charge separately for mainframe software[3][4][page needed] and services, by unbundling hardware and software.[5]

Bill Gates' "Open Letter to Hobbyists" in 1976 decried computer hobbyists' rampant copyright infringement of softwere, particularly Microsoft's Altair BASIC interpreter. He argued that hobbyists could not expect to have quality software available to them if they deny compensation to programmers.[6]

According to Brewster Kahle the legal characteristic of software changed also due to the U.S. Copyright Act of 1976.[7]

Starting in February 1983 IBM adopted an "object-code-only" model for a growing list of their software and stopped shipping source code.[8][9]

In 1983 binary software became also copyrightable by the Apple vs. Franklin law decision,[10] before that only source code was copyrightable.[11] Additionally, the growing availability of millions of computers based on the same microprocessor architecture created for the first time an unfragmented and big enough market for binary distributed software.[11]

Legal basis

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Most software is covered by copyright which, along with contract law, patents, and trade secrets, provides legal basis for its owner to establish exclusive rights.[12]

A software vendor delineates the specific terms of use in an end-user license agreement (EULA). The user may agree to this contract in writing, interactively, called clickwrap licensing, or by opening the box containing the software, called shrink wrap licensing. License agreements are usually not negotiable.[13]

Software patents grant exclusive rights to algorithms, software features, or other patentable subject matter. Laws on software patents vary by jurisdiction and are a matter of ongoing debate. Vendors sometimes grant patent rights to the user in the license agreement.[14]

Proprietary software vendors usually regard source code as a trade secret.[15]

Free software licenses and open-source licenses use the same legal basis as proprietary software.[16] Free software companies and projects are also joining into patent pools like the Patent Commons and the Open Invention Network.

Limitations

License agreements do not override applicable copyright law or contract law. Provisions that conflict may not be enforceable.[17]

Some vendors say that software licensing is not a sale, and that limitations of copyright like the first-sale doctrine do not apply. The EULA for Microsoft Windows states that the software is licensed, not sold.[18]

Exclusive rights

The owner of proprietary software exercises certain exclusive rights over the software. The owner can restrict use, inspection of source code, modification of source code, and redistribution.

Use of the software

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Vendors typically limit the number of computers on which software can be used, and prohibit the user from installing the software on extra computers.[citation needed] Restricted use is sometimes enforced through a technical measure, such as product activation, a product key or serial number, a hardware key, or copy protection.

Vendors may also distribute versions that remove particular features, or versions which allow only certain fields of endeavor, such as non-commercial, educational, or non-profit use.

Use restrictions vary by license:

  • Windows Vista Starter is restricted to running a maximum of three concurrent applications.
  • The retail edition of Microsoft Office Home and Student 2007 is limited to non-commercial use on up to three devices in one household.
  • Windows XP can be installed on one computer, and limits the number of network file sharing connections to 10.[19] The Home Edition disables features present in Windows XP Professional.
  • Traditionally Adobe licenses are limited to one user, but allow the user to install a second copy on a home computer or laptop.[20] This is no longer true with the switching to Creative Cloud.
  • iWork '09, Apple's productivity suite, is available in a five-user family pack, for use on up to five computers in a household.[21]

Inspection and modification of source code

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Vendors typically distribute proprietary software in compiled form, usually the machine language understood by the computer's central processing unit. They typically retain the source code, or human-readable version of the software, written in a higher level programming language.[22] This scheme is often referred to as closed source.[23]

By withholding source code, the software producer prevents the user from understanding how the software works and from changing how it works.[24] This practice is denounced by some critics, who argue that users should be able to study and change the software they use, for example, to remove secret or malicious features, or look for security vulnerabilities. Richard Stallman, founder of the Free Software Foundation, says that proprietary software commonly contains "malicious features, such as spying on the users, restricting the users, back doors, and imposed upgrades."[25] Some proprietary software vendors say that retaining the source code makes their software more secure, because the widely available code for open-source software makes it easier to identify security vulnerabilities.[26] Open-source proponents pejoratively call this security through obscurity, and say that wide availability results in increased scrutiny of the source code, making open-source software more secure.[27]

While most proprietary software is distributed without the source code, some vendors distribute the source code or otherwise make it available to customers. For example, users who have purchased a license for the Internet forum software vBulletin can modify the source for his or her own site but cannot redistribute it. This is true for many web applications, which must be in source code form when being run by a web server. The source code is covered by a non-disclosure agreement or a license that allows, for example, study and modification, but not redistribution.[citation needed] The text-based email client Pine and certain implementations of Secure Shell are distributed with proprietary licenses that make the source code available.[citation needed]

Some governments fear that proprietary software may include defects or malicious features which would compromise sensitive information. In 2003 Microsoft established a Government Security Program (GSP) to allow governments to view source code and Microsoft security documentation, of which the Chinese government was an early participant.[28][29] The program is part of Microsoft's broader Shared Source Initiative which provides source code access for some products. The Reference Source License (Ms-RSL) and Limited Public License (Ms-LPL) are proprietary software licenses where the source code is made available.

Governments have also been accused of adding such malware to software themselves. According to documents released by Edward Snowden, the NSA has used covert partnerships with software companies to make commercial encryption software exploitable to eavesdropping, or to insert backdoors.[30][31]

Software vendors sometimes use obfuscated code to impede users who would reverse engineer the software.[citation needed] This is particularly common with certain programming languages.[citation needed] For example, the bytecode for programs written in Java can be easily decompiled to somewhat usable code,[citation needed] and the source code for programs written in scripting languages such as PHP or JavaScript is available at run time.[32]

Redistribution

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Proprietary software vendors can prohibit users from sharing the software with others. Another unique license is required for another party to use the software.

In the case of proprietary software with source code available, the vendor may also prohibit customers from distributing their modifications to the source code.

Shareware is closed-source software whose owner encourages redistribution at no cost, but which the user sometimes must pay to use after a trial period. The fee usually allows use by a single user or computer. In some cases, software features are restricted during or after the trial period, a practice sometimes called crippleware.

Interoperability with software and hardware

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Proprietary file formats and protocols

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Proprietary software often[citation needed] stores some of its data in file formats which are incompatible with other software, and may also communicate using protocols which are incompatible. Such formats and protocols may be restricted as trade secrets or subject to patents.[citation needed]

Proprietary APIs

A proprietary application programming interface (API) is a software library interface "specific to one device or, more likely to a number of devices within a particular manufacturer's product range."[33] The motivation for using a proprietary API can be vendor lock-in or because standard APIs do not support the device's functionality.[33]

The European Commission, in its March 24, 2004 decision on Microsoft's business practices,[34] quotes, in paragraph 463, Microsoft general manager for C++ development Aaron Contorer as stating in a February 21, 1997 internal Microsoft memo drafted for Bill Gates:

The Windows API is so broad, so deep, and so functional that most ISVs would be crazy not to use it. And it is so deeply embedded in the source code of many Windows apps that there is a huge switching cost to using a different operating system instead.

Early versions of the iPhone SDK were covered by a non-disclosure agreement. The agreement forbade independent developers from discussing the content of the interfaces. Apple discontinued the NDA in October 2008.[35]

Vendor lock-in

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

A dependency on the future versions and upgrades for a proprietary software package can create vendor lock-in, entrenching a monopoly position.[36]

Software limited to certain hardware configurations

Proprietary software may also have licensing terms that limit the usage of that software to a specific set of hardware. Apple has such a licensing model for Mac OS X, an operating system which is limited to Apple hardware, both by licensing and various design decisions. This licensing model has been affirmed by the United States Court of Appeals.[37]

Abandonment by owners

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Proprietary software which is no longer marketed, supported or sold by its owner is called abandonware, the digital form of orphaned works. If the proprietor of a software package should cease to exist, or decide to cease or limit production or support for a proprietary software package, recipients and users of the package may have no recourse if problems are found with the software. Proprietors can fail to improve and support software because of business problems.[38] Support for older or existing versions of a software package may be ended to force users to upgrade and pay for newer versions[39] (Planned obsolescence). Sometimes another vendor or a software's community themselves can provide support for the software, or the users can migrate to either competing systems with longer support life cycles or to FOSS-based systems.[40]

Some closed-source software is released by their owner at end-of-life as open-source or source available software, often to prevent the software from becoming unsupported and unavailable abandonware.[41][42][43] 3D Realms and id software are famous for the practice of releasing closed source software into the open source. Some of those kinds are free-of-charge downloads (freeware), some are still commercially sold (e.g. Arx Fatalis). More examples of formerly closed-source software in the List of commercial software with available source code and List of commercial video games with available source code.

Formerly open-source software

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Some formerly open-source software was made proprietary later. Sometimes for commercialization reasons, sometimes as security or anti-cheat measurement (Security through obscurity). A famous example of such is the Doom source port ZDaemon which was prone to aimbot cheaters.[44]

Pricing and economics

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Proprietary software is not synonymous with commercial software,[45][46] though the industry commonly confuses the term,[47][48] as do some articles about free software.[49][50] Proprietary software can be distributed at no cost or for a fee, and free software can be distributed at no cost or for a fee.[51] The difference is that whether or not proprietary software can be distributed, and what the fee would be, is at the proprietor's discretion. With free software, anyone who has a copy can decide whether, and how much, to charge for a copy or related services.[52]

Proprietary software that comes for no cost is called freeware.

Proponents of commercial proprietary software argue that requiring users to pay for software as a product increases funding or time available for the research and development of software. For example, Microsoft says that per-copy fees maximise the profitability of software development.[53]

Proprietary software generally creates greater commercial activity over free software, especially in regard to market revenues.[54]

Similar terms

A related concept is closed platform or "walled garden". The term "silo" is used to describe the even broader notion of "closed habitats that serve as private marketplaces that lock customers in and competitors out".[60][61]

Examples

Examples of proprietary software include Microsoft Windows, Adobe Flash Player, PS3 OS, iTunes, Adobe Photoshop, Google Earth, Mac OS X, Skype, WinRAR, Oracle's version of Java and some versions of Unix.

Software distributions considered as proprietary may in fact incorporate a "mixed source" model including both free and non-free software in the same distribution.[62] Most if not all so-called proprietary UNIX distributions are mixed source software, bundling open-source components like BIND, Sendmail, X Window System, DHCP, and others along with a purely proprietary kernel and system utilities.[63][64]

Some free software packages are also simultaneously available under proprietary terms. Examples include MySQL, Sendmail and ssh. The original copyright holders for a work of free software, even copyleft free software, can use dual-licensing to allow themselves or others to redistribute proprietary versions. Non-copyleft free software (i.e. software distributed under a permissive free software license or released to the public domain) allows anyone to make proprietary redistributions.[65][66] Free software that depends on proprietary software is considered "trapped" by the Free Software Foundation. This includes software written only for Microsoft Windows,[67] or software that could only run on Java, before it became free software.[68]

In India, one and a half million laptops were pre-loaded with screen savers of political minister Mulayam Singh Yadav. The author of software developed for these laptops included a malicious feature that would "crash" the device if the laptop's owner attempted to change, remove, or modify this feature.[69]

See also

<templatestyles src="Div col/styles.css"/>

2

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Robert X. Cringely's interview with Brewster Kahle, 46th minute
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Impact of Apple vs. Franklin Decision
  11. 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Limitations and Exceptions to Copyright and Neighbouring Rights in the Digital Environment: An International Library Perspective (2004). IFLA (2013-01-22). Retrieved on 2013-06-16.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. iWork '09 Family Pack Specs (complete package) - Presentation - CNET Reviews. Reviews.cnet.com. Retrieved on 2013-06-16.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Why Open Source Misses the Point of Free Software - GNU Project - Free Software Foundation. Gnu.org. Retrieved on 2013-06-16.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. The Truth About Open Source Security | Enterprise. TechNewsWorld. Retrieved on 2013-06-16.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. 33.0 33.1 APIs: What they are, and what they're for - Feature - Techworld.com. Features.techworld.com. Retrieved on 2013-06-16.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. ZDaemon Starting with the 1.07 release in July 2005, the ZDaemon project does not make the source code available anymore and has remained closed source from that point forward
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.