Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
IRCd
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{short description|Server software that implements IRC}} {{more citations needed section|date=September 2009}} An '''IRCd''', short for '''Internet Relay Chat [[daemon (computing)|daemon]]''', is [[server (computing)|server software]] that implements the [[Internet Relay Chat|IRC]] [[protocol (computing)|protocol]], enabling people to talk to each other via the [[Internet]] (exchanging [[text-based (computing)|textual]] messages in real time).<ref>{{cite journal|url=http://tools.ietf.org/html/rfc2810#section-4 |title=RFC 2810 - Internet Relay Chat: Architecture |year=2000 |publisher=Tools.ietf.org |doi=10.17487/RFC2810 |access-date=2010-03-03|last1=Kalt |first1=C. |url-access=subscription }}</ref><ref>[http://www.irchelp.org/irchelp/ircd/server-request.html IRC Server Request FAQ] {{webarchive|url=https://web.archive.org/web/20090422113612/http://www.irchelp.org/irchelp/ircd/server-request.html |date=2009-04-22 }}</ref> It is distinct from an [[Internet Relay Chat bot|IRC bot]] that connects outbound to an IRC channel. The server listens to connections from [[IRC client]]s<ref>{{cite journal|url=http://tools.ietf.org/html/rfc2810#section-2.1 |title=RFC 2810 β Internet Relay Chat: Architecture |year=2000 |publisher=Tools.ietf.org |doi=10.17487/RFC2810 |access-date=2010-03-03|last1=Kalt |first1=C. |url-access=subscription }}</ref> on a set of [[TCP and UDP port|TCP ports]].<ref name=RFC1459>{{cite journal|url=http://tools.ietf.org/html/rfc1459#section-1 |title=RFC 1459 β Internet Relay Chat Protocol |year=1993 |publisher=Tools.ietf.org |doi=10.17487/RFC1459 |access-date=2010-03-03|last1=Oikarinen |first1=J. |last2=Reed |first2=D. |url-access=subscription }}</ref> When the server is part of an IRC network, it also keeps one or more established connections to other servers/daemons.<ref>{{cite journal|url=http://tools.ietf.org/html/rfc1459#section-1.1 |title=RFC 1459 β Internet Relay Chat Protocol |year=1993 |publisher=Tools.ietf.org |doi=10.17487/RFC1459 |access-date=2010-03-03|last1=Oikarinen |first1=J. |last2=Reed |first2=D. |url-access=subscription }}</ref> The term ''ircd'' originally referred to only one single piece of software,<ref>[http://www.irc.org/tech_docs/ircnet/faq.html#ircd IRCD FAQ on irc.org]</ref> but it eventually became a generic reference to any implementation of an IRC daemon.<ref>{{cite web|url=http://searchirc.com/ircd-versions |title=Search IRC, IRCD version overview |publisher=Searchirc.com |access-date=2010-03-03}}</ref><ref>{{cite web|url=http://www.dmoz.org/Computers/Software/Internet/Servers/Chat/IRC/ |title=Open Directory β Computers: Software: Internet: Servers: Chat: IRC |publisher=Dmoz.org |date=2010-02-26 |access-date=2010-03-03}}</ref> However, the original version is still distributed under the same name,<ref>{{cite web|url=http://www.funet.fi/~irc/server/ |title=IRCD β the server |publisher=Funet.fi |access-date=2010-03-03}}</ref> and this article discusses both uses. == History == {{Update|section|date=January 2015}} <!-- IRCv3? --> The original IRCd was known as 'ircd', and was authored by [[Jarkko Oikarinen]] (WiZ on IRC) in 1988.<ref>[http://www.irc.org/history_docs/jarkko.html IRC History on IRC.org]</ref><ref>[http://daniel.haxx.se/irchistory.html History of IRC, Daniel Stenberg]</ref> He received help from a number of others, such as Markku Savela (msa on IRC), who helped with the 2.2+msa release, etc. In its first revisions, IRC did not have many features that are taken for granted today, such as named channels and [[Internet Relay Chat channel operator|channel operators]]. Channels were numbered – channel 4 and channel 57, for example – and the channel '''topic''' described the kind of conversation that took place in the channel. One holdover of this is that joining channel 0 causes a client to leave all the channels it is presently on: "CHANNEL 0" being the original command to leave the current channel. The first major change to IRC, in version 2.5, was to add '''named channels''' – "+channels". "+channels" were later replaced with "#channels" in version 2.7, numeric channels were removed entirely and channel bans (mode +b) were implemented. Around version 2.7, there was a small but notable dispute{{Clarify| reason=What was the acutal dispute?| date=March 2013}}, which led to ircu – the [[Undernet]] fork of ircd. irc2.8 added "&channels" (those that exist only on the current server, rather than the entire network) and "!channels" (those that are theoretically safe from suffering from the many ways that a user could exploit a channel by "[[IRC takeover|riding a netsplit]]"), and is the baseline release from which nearly all current implementations are derived. Around 2.8 came the concept of nick and channel delay, a system designed to help curb abusive practices such as [[IRC takeover|takeovers]] and split riding. This was not agreed on by the majority of modern IRC (EFnet, DALnet, Undernet, etc.) β and thus, 2.8 was forked into a number of different daemons using an opposing theory known as TS – or time stamping, which stored a unique time stamp with each channel or nickname on the network to decide which was the 'correct' one to keep. Time stamping itself has been revised several times to fix various issues in its design. The latest versions of such protocols are: * the TS6 protocol, which is used by [[EFnet]], and Hybrid and Ratbox based servers amongst others * the [[#P10|P10 protocol]], which is used by [[Undernet]] and ircu based servers. While the client-to-server protocols are at least functionally similar, [[server-to-server]] protocols differ widely (TS5, P10, and ND/CD server protocols are incompatible), making it very difficult to "link" two separate implementations of the IRC server. Some "bridge" servers do exist, to allow linking of, for example, 2.10 servers to TS5 servers, but these are often accompanied with restrictions of which parts of each protocol may be used, and are not widely deployed. Significant releases based on 2.8 included: * 2.8.21+CS, developed by Chris Behrens ('''Comstud''') * 2.8+th, Taner Halicioglu's patchset, which later became ** Hybrid IRCd, originally developed by Jon Lusky ('''Rodder''') and Diane Bruce ('''Dianora''') as 2.8/hybrid, later joined by a large development team. * 2.9, 2.10, 2.11, ... continue the development of the original codebase, The original code base continued to be developed mainly for use on the [[IRCnet]] network. New server-to-server protocols were introduced in version 2.10, released in 1998, and in 2.11, first released in 2004, and current {{As of|2007|lc=on}}. This daemon is used by [[IRCnet]] and it can be found at http://www.irc.org/ftp/irc/server/ The original ircd is [[free software]], licensed under the [[GNU General Public License]]. This development line produced the 4 IRC RFCs released after RFC 1459, which document this server protocol exclusively. 2.8.21+CS and Hybrid IRCd continue to be used on [[EFnet]], with ircd-ratbox (an offshoot of ircd-hybrid) {{As of|2004|lc=on}} being the most popular. === Sidestream versions === [[File:IRCd software implementations3.svg|thumb|right|Diagram of derivations and relations for common IRCd implementations.]] More recently, several irc daemons were written from scratch, such as ithildin,<ref>[http://www.ithildin.org/ Ithildin IRCd]</ref> InspIRCd,<ref>[http://www.inspircd.org/ Inspire IRCd]</ref> csircd (also written by Chris Behrens), ConferenceRoom,<ref>{{Cite web |url=http://www.conferenceroom.com/ |title=WebMaster Inc. |access-date=2020-01-20 |archive-url=https://web.archive.org/web/20160303213029/http://www.conferenceroom.com/ |archive-date=2016-03-03 |url-status=dead }}</ref> Microsoft Exchange Chat Service, WeIRCd,<ref>{{Cite web |url=http://eloxoph.com/weircd/ |title=WeIRCd |access-date=2009-03-26 |archive-url=https://web.archive.org/web/20100514140803/http://eloxoph.com/weircd/ |archive-date=2010-05-14 |url-status=usurped }}</ref> or IRCPlus/IRCXPro.<ref>[http://www.ircxpro.com OfficeIRC β IRC Server Software, Web Chat, Internal Communications and Instant Messaging (IM)]</ref> These attempts have met with mixed success, and large doses of skepticism from the existing IRC development community. With each new IRCd, a slightly different version of the IRC protocol is used,<ref>[http://smartirc4net.meebey.net/jaws/index.php?blog/show/SmartIrc4net_035_released Blog entry mentioning RFC violations]</ref><ref>[http://www.alien.net.au/irc/irc2numerics.html Numerics diversity of different IRC daemons]</ref> and many [[IRC client]]s and [[IRC bot|bots]] are forced to compromise on features or vary their implementation based on the server to which they are connected.<ref>[http://git.dmdirc.com/cgit.cgi/parser/tree/src/com/dmdirc/parser/irc/IRCParser.java Client source (DMDirc) showing conditions for different servers (e.g. in function starting at line 1523)]</ref> These are often implemented for the purpose of improving usability, security, separation of powers, or ease of integration with [[IRC services|services]]. Possibly one of the most common and visible differences is the inclusion or exclusion of the half-op [[Internet Relay Chat channel operator|channel operator]] status (which is not a requirement of the RFCs). == Features == === Ports === The officially assigned port numbers are 194 ("irc"), 529 ("irc-serv"), and 994 ("ircs").<ref>[https://www.iana.org/assignments/port-numbers IANA.org]</ref> However, these ports are in the ''privileged'' range (0β1024), which on a [[Unix-like]] system means that the daemon would historically have to have [[superuser]] privileges in order to open them. For various [[security]] reasons this used to be undesirable. The common ports for an IRCd process are 6665 to 6669, with 6667 being the historical default.<ref>{{cite journal|url=http://tools.ietf.org/html/rfc1459#section-5.6 |title=RFC 1459 β Internet Relay Chat Protocol |year=1993 |publisher=Tools.ietf.org |doi=10.17487/RFC1459 |access-date=2010-03-03|last1=Oikarinen |first1=J. |last2=Reed |first2=D. |url-access=subscription }}</ref> These ports can be opened by a non-superuser process, and they became widely used. === Connections === Running a large IRC server, one that has more than a few thousand simultaneous users, requires keeping a very large number of [[Transmission Control Protocol|TCP connections]] open for long periods. Very few ircds are [[Thread (computer science)|multithreaded]] as nearly every action needs to access (at least read and possibly modify) the global state. The result is that the best platforms for ircds are those that offer efficient mechanisms for handling huge numbers of connections in a single thread. [[Linux kernel|Linux]] offers this ability in the form of [[epoll]], in kernel series newer than 2.4.x. [[FreeBSD]] (since 4.1) and OpenBSD (since 2.9) offers [[kqueue]]. [[Solaris (operating system)|Solaris]] has had [https://web.archive.org/web/20070202231908/http://access1.sun.com/techarticles/devpoll.html /dev/poll] since version 7, and from version 10 onwards has [[IOCP]] (I/O Completion Ports). [[Windows]] has supported [[IOCP]] since Windows NT 3.5. The difference made by these new interfaces can be dramatic. IRCU developers have mentioned increases in the practical capacity per server from 10,000 users to 20,000 users.{{Citation needed|reason=Which developers? and When? |date=July 2022}} === TLS (Transport Layer Security) === Some IRCd support [[Transport Layer Security]], or TLS, for those who don't, it is still possible to use SSL via [[Stunnel]]. The unofficial, but most often used port for TLS IRCd connections is [[List of TCP and UDP port numbers#Registered ports|6697]]. More recently, as a security enhancement and usability enhancement, various client and server authors have begun drafting a standard known as the STARTTLS standard<ref>{{Cite web |url=http://www.inspircd.org/wiki/STARTTLS_Documentation |title=STARTTLS standard |access-date=2008-07-20 |archive-url=https://web.archive.org/web/20080624222000/http://www.inspircd.org/wiki/STARTTLS_Documentation |archive-date=2008-06-24 |url-status=dead }}</ref> which allows for TLS and plain text connections to co-exist on the same TCP port. === IPv4 and IPv6 === IRC daemons support [[IPv4]], and some also support [[IPv6]]. In general, the difference between IPv6 and IPv4 connections to IRC is purely academic and the service operates in much the same manner through either protocol. === Clustering === Large IRC networks consist of multiple servers for [[horizontal scaling]] purposes. There are several IRC protocol extensions for these purposes.<ref name=scale>Paul Mutton, ''IRC hacks'', [[O'Reilly Media]], 2004, {{ISBN|0-596-00687-X}}, pp. 371</ref> ==== IRCX ==== [[IRCX]] (Internet Relay Chat eXtensions) is an extension to the IRC protocol developed by Microsoft<br/> ==== P10 ==== The '''P10''' protocol is an extension to the [[Internet Relay Chat]] protocol for server to server communications developed by the Undernet Coder Committee to use in their ircu server software. It is similar in purpose to [[IRCX]] and EFnet TS5/TS6 protocols and implements nick and channel timestamping for handling nick collisions and netsplit channel riding, respectively. Other IRCd's that utilize this protocol extension include [[bIRCd|beware ircd]].<ref name=scale/><ref>[http://ircd.bircd.org/bewarep10.txt beware's P10 documentation]</ref><ref>[http://web.mit.edu/klmitch/Sipb/devel/src/ircu2.10.11/doc/p10.html ircu P10 documentation]</ref> ==== TS6 ==== The '''TS6''' protocol is an extension to the [[Internet Relay Chat]] protocol for server to server communications developed initially by the developers of ircd-ratbox. It has been extended by various IRC software and has the feature that proper implementations of TS6 can link to each other by using feature negotiationβeven if features are disparate. == Configuration == === Jupe === '''Juping''' a server, a channel, or a nickname refers to the practice of blocking said channel or nickname on the [[server (computing)|server]] or [[computer network|network]] or said server on the network. One possible explanation of how this term came about is that it is named after the [[IRC operator|oper]] named Jupiter, who gained control of the nickname [[NickServ]] on [[EFnet]].<ref>{{cite web|url=http://forum.efnet.org/viewtopic.php?p=736&sid=93438e76e1948098a2575a7474b56cbd#p736|access-date=2013-03-13|title=Reply to thread "K-lined for {{sic|nolink=y|attemting}} to join juped channel ?" on EFnet forums}}</ref>{{Citation needed|date=September 2009}} EFnet does not offer services such as NickServ; Jupiter gained control of the nickname as he (among other operators) did not believe nicknames should be owned. Today, EFnet opers jupe nicknames that are used as services on other networks. A nickname or server jupe takes advantage of the fact that certain identifiers are unique; by using an identifier, one acquires an exclusive lock that prevents other users from making use of it. Officially sanctioned jupes may also utilize services or server configuration options to enforce the jupe, such as when a compromised server is juped to prevent it from harming the network. In practice IRC operators now use jupe configurations to administratively make channel or nicknames unavailable.<ref>{{cite web|url=http://freenode.net/using_the_network.shtml|access-date=2007-02-25|title=Freenode, Using the network|url-status=dead|archive-url=https://web.archive.org/web/20070226012149/http://freenode.net/using_the_network.shtml|archive-date=2007-02-26}}</ref> A channel jupe refers to a server specific ban of a channel, which means that a specific channel cannot be joined when connected to a certain server, but other servers may allow a user to join the channel. This is a way of banning access to problematic channels. === O-line {{anchor|O-line}} === An '''O-line''' (frequently also spelled as '''O:line'''{{citation needed|date=March 2013}}; on IRCds that support local operators, the O-lines of those are called '''o:lines''' with a lower-case O{{citation needed|date=March 2013}}), shortened from ''Operator Line'' and derived from the line-based configuration file of the original IRCd, is a line of code in an IRC daemon configuration file that determines which users can become an [[IRC operator]] and which permissions they get upon doing so. The name comes from the prefix used for the line in the original IRCd, a capital O. The O-line specifies the username, password, operator flags, and hostmask restrictions for a particular operator. A server may have many O-lines depending on the administrative needs of the server and network.<ref>[http://docs.dal.net/docs/operinfo.html IRC Operator Version 1.1.2]</ref> Operator flags are used to describe the permissions an operator is granted. While some IRC operators may be in charge of network routing, others may be in charge of network abuse, making their need for certain permissions different.<ref name=RFC1459 /> Operator flags available vary widely depending on which IRC daemon is in use. Generally, more feature rich IRC daemons tend to have more operator flags, and more traditional IRC daemons have fewer. An O-line may also be set so that only users of a certain [[hostmask]] or [[IP address]] can gain IRC operator status using that O-line. Using hostmasks and IP addresses in the O-line requires the IP address to remain the same but provides additional security. === K-line === When a user is ''k-lined'' (short for '''kill line'''), the user is banned from a certain server, either for a certain amount of time or permanently. Once the user is banned, they are not allowed back onto that server. This is recorded as a line in the server's IRC daemon configuration file prefixed with the letter "K", hence "K-line". Some IRC daemons, including ircd-hybrid and its descendants, can be configured to propagate K-lines to some or all other servers on a network. In such a configuration, K-lines are effectively global bans similar to G-lines. While the precise reason for the disconnection varies from case to case, usual reasons involve some aspect of the client or the user it is issued against. ; User behavior : K-lines can be given due to inappropriate behavior on the part of the user, such as "nickname colliding", mode "hacking", multiple channel flooding, harassing other users via [[private message|private messaging]] features, "[[spamming]]" etc., or in the case of older networks without timestamping, [[split riding]], which cannot be corrected through use of [[Internet Relay Chat channel operator|channel operator]] privileges alone. ; Client software : Some IRC daemons can be configured to scan for viruses or other vulnerabilities in clients connecting to them, and will react in various ways according to the result. Outdated and insecure client software might be blocked to protect other network users from vulnerabilities, for instance. Some networks will disconnect clients operating on/via open [[proxy server|proxies]], or running an insecure web server. ; Geographic location : An IRC network operating multiple servers in different locales will attempt to reduce the distance between a client and a server. This is often achieved by disconnecting (and/or banning) clients from distant locales in favour of local ones. There are a number of other network "lines" relating to the K-line. Modern IRC daemons will also allow IRC operators to set these lines during normal operation, where access to the server configuration file is not routinely needed. === G-line === {{Redirect|G-line}} A '''G-line''' or '''global kill line''' (also written '''G:line''') is a global network ban applied to a user; the term comes from [[Undernet]] but on [[DALnet]] a similar concept known as an [[AKill]] was used.{{Citation needed|date=February 2019}} G-lines are sometimes stored in the [[configuration file]] of the IRCd, although some networks, who handle K-lines through the [[IRC services]], prefer to have them stored in their service's configuration files. Whenever a G-lined person attempts to connect to the IRC network, either the services or the IRC daemon will automatically disconnect the client, often displaying a message explaining the reasoning behind the ban. G-lines are a variant of K-lines, which work in much the same way, except K-lines only disconnect clients on one server of the network. G-lines are normally applied to a user who has received a K-line on one server but continues to abuse the network by connecting via a different server. G-lines are often regarded as an extreme measure, only to be used in cases of repeated abuse when extensive attempts have been made to reason with the offending user. Therefore, especially on larger networks, often only very high ranking global [[IRC operator]]s are permitted to set them, while K-lines, which are mostly regarded as a local affair, are left to the operators of the individual [[server (computing)|server]] in the network. G-lines also work slightly differently from K-lines. G-lines are typically set as *@IPaddress or *@host, with the first being the better option. If the *@host option is used, the server must conduct a reverse DNS lookup on the user and then compare the returned host to the hosts in the G-line list. This results in delay, and, if the DNS doesn't return correct results, the banned user may still get on the network. === Z-line {{anchor|GZ-line|D-line|X-line}} === {{Redirect|Zline||Z-line (disambiguation){{!}}Z-line}} A '''Z-line''' or '''zap line''' (also written '''Z:line''') is similar to a K-line, but applied to a client's IP address range, and is considered to be used in extreme cases. Because a Z-line does not have to check usernames (identd) or ''resolved'' hostnames, it can be applied to a user before they send any data at all upon connection. Therefore, a Z-line is more efficient and uses fewer resources than a K-line or G-line when banning large numbers of users. In some IRC daemons such as ircd-hybrid, this is called a '''D-line''' (deny line) or an '''X-line'''. Z-lines are sometimes stored in the configuration file of the IRCd, although some networks, who handle lines through the IRC services, prefer to have them stored in their service's configuration files. Whenever a Z-lined person attempts to connect to the IRC network, either the services or the IRC daemon will automatically disconnect the client, often displaying a message explaining the reasoning behind the ban. Z-lines are a variant of K-lines, which work in much the same way. Most Z-lines are "awarded" to people who abuse the network as a whole (on smaller networks, these are more frequently issued for isolated incidents). Z-lines also work slightly differently from K-lines. Z-lines are typically set as *@IP or *@host, with the first being the better option. Z-lines do not wait for an ident response from the connecting user, but immediately close the socket once the user's IP is compared to the Z-line list and a match is found. If the *@host option is used, the server must conduct a reverse DNS lookup on the user and then compare the returned host to the hosts in the Z-line list. This can result in delays, or if the DNS doesn't return correctly, banned users could still get on the network. In actuality, the *@host option is completely against the intentions of using a Z-line, and therefore some IRCd programs will not allow anything other than *@IP, with [[wildcard character|wildcards]] (?,*) or [[Classless Inter-Domain Routing|CIDR prefix lengths]] (''e.g. /8)'' allowed in the IP section to block entire subnets. Another difference from K-lines (which affect only IRC clients) is if an IP is banned, nothing, not even other servers, can connect from this IP (or IP range, depending on the banmask). One advantage to using Z-lines over K-lines and G-lines, from a server or network administrator's perspective, a Z-line uses less bandwidth than a K-line, mainly because it doesn't wait for an [[ident protocol|ident]] response or [[Domain Name System|DNS]] lookup. A disadvantage to using Z-line over K-line or G-line is that it becomes more difficult to ban entire ISPs and very dynamic IP addresses, common with some [[dialup]] and [[Digital subscriber line|DSL]] connections. For example, if a network administrator wants to ban all of ISP example.com (with hypothetical [[IP address]] ranges of 68.0.0.0 β 68.255.255.255 and 37.0.0.0 β 38.255.255.255), a G-line could use *@*example.com, whereas Z-line would require *@37.*.*.*, *@38.*.*.*, and *@68.*.*.* to accomplish the same thing. Z-lines can also be global, in which case they are called '''GZ-lines'''. GZ-lines work in the same manner as Z-lines, except that they propagate to every server on the network. Some IRC daemons may also be configured to share Z-lines with other servers. === Q-line === {{Redirect|Q-line|the New York City subway service|Q (New York City Subway service)|the Detroit streetcar service|QLine}} On some IRCds, such as UnrealIRCd, a '''Q-line''' forbids a nickname, or any nickname matching a given pattern. This is most often used to forbid use of services nicknames (such as "X", or [[NickServ]]) or forbid use of [[IRC operator]] nicknames by non-operators. Some IRC daemons may disconnect users when initially applying the Q-line, whilst others will force a nickname change, or do nothing until the user covered by the Q-line reconnects. Other IRCds, like ircd-hybrid, use the "RESV" ("reserve") command instead, with the stats letter remaining as Q. The "RESV" command can also forbid a channel from being used. == See also == * [[Internet Relay Chat services]] == References == {{Reflist|30em}} == External links == * [http://www.irc.org irc.org β IRC resources] {{deadlink|date=January 2025}} * [http://www.irc.org/tech_docs/TS-Delay.html Technical comparison of TS and nickname delay mechanisms] * [https://web.archive.org/web/20080404160036/http://www.darkfire.net/irc/docs/opermanual.shtml DarkFire IRC Manual (network specific)] * [http://www.user-com.undernet.org/documents/k-gline.txt Undernet K-Line and G-Line FAQ] {{Webarchive|url=https://web.archive.org/web/20080401093403/http://www.user-com.undernet.org/documents/k-gline.txt |date=2008-04-01 }} with reasons for them, amongst other things * [https://web.archive.org/web/20080827185523/http://www.efnet.info/faq.html EFnet FAQ] with several -line terms explained * [http://www.quakenet.org/faq/faq.php?f=11#11 Quakenet General FAQ] G/K-Line * [https://web.archive.org/web/20080323045540/http://www.inspircd.org/wiki/Commands#.2FKLINE_.5Buser.40host.5D_.7B.5Bduration.5D_:.5Breason.5D.7D GLine, KLine, QLine and ELine syntax] {{IRC daemons}} [[Category:IRC]] [[Category:Free and open-source software]]
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)
Pages transcluded onto the current version of this page
(
help
)
:
Template:Anchor
(
edit
)
Template:As of
(
edit
)
Template:Citation needed
(
edit
)
Template:Cite journal
(
edit
)
Template:Cite web
(
edit
)
Template:Clarify
(
edit
)
Template:Deadlink
(
edit
)
Template:IRC daemons
(
edit
)
Template:ISBN
(
edit
)
Template:More citations needed section
(
edit
)
Template:Redirect
(
edit
)
Template:Reflist
(
edit
)
Template:Short description
(
edit
)
Template:Update
(
edit
)
Template:Webarchive
(
edit
)