Jump to content

ISC license

From Wikipedia, the free encyclopedia
(Redirected from ISC License)

ISC license
PublisherInternet Systems Consortium
SPDX identifierISC
Debian FSG compatibleYes[1]
FSF approvedYes[2]
OSI approvedYes[3]
GPL compatibleYes[2]
CopyleftNo[2]
Linking from code with a different licenceYes
Websitewww.isc.org/licenses/ Edit this at Wikidata

The ISC license is a permissive free software license published by the Internet Software Consortium, now called Internet Systems Consortium (ISC). It is functionally equivalent to the simplified BSD and MIT licenses, but without language deemed unnecessary following the Berne Convention.[nb 1][nb 2]

Originally used for ISC software such as BIND and dig, it has become the preferred license for contributions to OpenBSD[6] and the default license for npm packages.[7] The ISC license is also used for Linux wireless drivers contributed by Qualcomm Atheros,[8] as well as by the LV2 plugin system.[9]

License terms

[edit]
ISC License

Copyright <2024> <Mervyn Dow>

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
— [10][11]

When initially released, the license did not include the term "and/or", which was changed from "and" by ISC in 2007.[12] Paul Vixie stated on the BIND mailing list that the ISC license started using the term "and/or" to avoid controversy similar to the events surrounding the University of Washington's refusal to allow distribution of the Pine email software.[12] Both versions of the license are compatible with the GNU GPL.[2]

OpenBSD license

[edit]

The OpenBSD project began using the ISC license in 2003, before the 2007 addition of the term "and/or" to the license.[13] 

Copyright (c) YYYY YOUR-NAME-HERE <user@your.dom.ain>

Permission to use, copy, modify, and distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
— [6]

Theo de Raadt of OpenBSD chose to retain the original wording, stating that he "disagrees with what ISC did" and is "not confident that their change is good" because "some country's legal systems might not understand 'and/or' in the way the old 'or' was used in the sentence".[5]

Reception

[edit]

In 2015, ISC announced they would release their Kea DHCP Software under the Mozilla Public License 2.0, stating, "There is no longer a good reason for ISC to have its own license, separate from everything else".[14] They also preferred a copyleft license, stating, "If a company uses our software but improves it, we really want those improvements to go back into the master source". Throughout the following years, they re-licensed all ISC-hosted software, including BIND in 2016[15] and ISC DHCP Server in 2017.[16]

The Publications Office of the European Union advises using the MIT license instead of the ISC License in order to reduce license proliferation.[17]

The GNU project states the inclusion of "and/or" still allows the license to be interpreted as prohibiting distribution of modified versions. Although they state there is no reason to avoid software released under this license, they advise against using the license to keep the problematic language from causing trouble in the future.[18]

See also

[edit]

Footnotes

[edit]
  1. ^ "The ISC copyright is functionally equivalent to a two-term BSD copyright with language removed that is made unnecessary by the Berne convention."[4]
  2. ^ "In OpenBSD we use an ISC-style copyright text [...] that is enough to satisfy every legal system on the planet which follows the Berne Convention."[5]

References

[edit]
  1. ^ "License information". The Debian Project. Software in the Public Interest (published 12 July 2017). 1997–2017. Archived from the original on 20 July 2017. Retrieved 20 July 2017. ... This page presents the opinion of some debian-legal contributors on how certain licenses follow the Debian Free Software Guidelines (DFSG). ... Licenses currently found in Debian main include:
    • ...
    • Expat/MIT-style licenses
    • ...
  2. ^ a b c d "Various Licenses and Comments about Them". The GNU Project. Free Software Foundation (published 4 April 2017). 2014–2017. ISC License. Archived from the original on 20 July 2017. Retrieved 20 July 2017. ... This is a lax, permissive free software license, and compatible with the GNU GPL. ... This license is sometimes also known as the OpenBSD License, although there is one minor difference between the two licenses. The OpenBSD license was updated to remove the ambiguous term: "and/or". ... At the time the ISC license was released, the use of "and/or" construct was a concern because it is similar language used in the license of Pine that the University of Washington later claimed prohibited people from distributing modified versions of the software. ...
  3. ^ "Licenses by Name". Open Source Initiative. n.d. Archived from the original on 20 July 2017. Retrieved 20 July 2017. ... The following licenses have been approved by the OSI. ...
    • ...
    • ISC License (ISC)
    • ...
  4. ^ "Copyright Policy". OpenBSD. Retrieved 6 June 2016.
  5. ^ a b de Raadt, Theo (21 March 2008). "Re: BSD Documentation License?". openbsd-misc (Mailing list). Retrieved 17 March 2017.
  6. ^ a b "OpenBSD license template". Retrieved 17 March 2017.
  7. ^ Oxley, Tim (8 January 2014). "Update default license to ISC". npm/init-package-json. Pull Request #9. Retrieved 17 March 2017.
  8. ^ "en/users/Drivers/Atheros - Linux Wireless". linuxwireless.org. Archived from the original on 21 June 2017. Retrieved 15 July 2017.
  9. ^ "COPYING · master · LV2 / lv2 · GitLab". gitlab.com. Retrieved 10 August 2023.
  10. ^ "ISC License (ISC)". Open Source Initiative. Retrieved 15 July 2017.
  11. ^ "ISC License". Software Package Data Exchange. Retrieved 9 July 2021.
  12. ^ a b Vixie, Paul (20 July 2007). "BIND covered under which license and does it conatin any cryptographic content ?". Newsgroup: comp.protocols.dns.bind. Retrieved 15 July 2017 – via Google Groups.
  13. ^ "src/share/misc/license.template - view - 1.1". 3 June 2003.
  14. ^ "Kea to be released under Mozilla Public License 2.0 - Internet Systems Consortium". www.isc.org. 8 December 2015. Retrieved 18 July 2020.
  15. ^ "BIND 9 Adopts the MPL 2.0 License with BIND 9.11.0 - Internet Systems Consortium". www.isc.org. 27 June 2016. Retrieved 18 July 2020.
  16. ^ "ISC DHCP Moves to MPL 2.0 License - Internet Systems Consortium". www.isc.org. 19 June 2017. Retrieved 18 July 2020.
  17. ^ "ISC License (ISC) - EU Vocabularies - Publications Office of the EU". op.europa.eu. Retrieved 18 July 2020.
  18. ^ "Various Licenses and Comments about Them". www.gnu.org. Retrieved 18 July 2020.
[edit]
Retrieved from "https://wiki.riteme.site/w/index.php?title=ISC_license&oldid=1262716967"