<feed xmlns='http://www.w3.org/2005/Atom'>
<title>ngircd/doc/sample-ngircd.conf, branch rel-19.2</title>
<subtitle>ngircd with make
</subtitle>
<id>http://git.nakidai.ru/ngircd/atom?h=rel-19.2</id>
<link rel='self' href='http://git.nakidai.ru/ngircd/atom?h=rel-19.2'/>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/'/>
<updated>2010-11-03T19:41:42+00:00</updated>
<entry>
<title>doc: change path names in sample-ngircd.conf depending on sysconfdir</title>
<updated>2010-11-03T19:41:42+00:00</updated>
<author>
<name>Florian Westphal</name>
<email>fw@strlen.de</email>
</author>
<published>2010-11-01T22:47:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=4a197638688d4e39d57f201ac735a38c9fc5a260'/>
<id>urn:sha1:4a197638688d4e39d57f201ac735a38c9fc5a260</id>
<content type='text'>
</content>
</entry>
<entry>
<title>New configuration option "NoZeroConf" to disable ZeroConf registration</title>
<updated>2010-10-11T14:54:49+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2010-10-11T14:54:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=a988bbc86aed404b7bcfdbceafc030ea4bc5ecab'/>
<id>urn:sha1:a988bbc86aed404b7bcfdbceafc030ea4bc5ecab</id>
<content type='text'>
If ngIRCd is compiled to register its services using ZeroConf (e.g. using
Howl, Avahi or on Mac OS X) this parameter can be used to disable service
registration at runtime.
</content>
</entry>
<entry>
<title>New configuration option "SyslogFacility"</title>
<updated>2010-09-24T15:39:11+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2010-09-24T15:39:11+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=5e82a91d1337b78510bc62fe3c7e43f9c0b7d3d1'/>
<id>urn:sha1:5e82a91d1337b78510bc62fe3c7e43f9c0b7d3d1</id>
<content type='text'>
The new option "SyslogFacility" deines the syslog "facility" to which
ngIRCd should send log messages.

Possible values are system dependant, but most probably "auth", "daemon",
"user" and "local1" through "local7" are possible values; see syslog(3).
Default is "local5" for historical reasons.
</content>
</entry>
<entry>
<title>ngircd: change MOTD file handling</title>
<updated>2010-08-12T19:46:47+00:00</updated>
<author>
<name>Florian Westphal</name>
<email>fw@strlen.de</email>
</author>
<published>2010-08-11T20:52:06+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=056de78e315a79edc1166649514bf8dfeb18abb1'/>
<id>urn:sha1:056de78e315a79edc1166649514bf8dfeb18abb1</id>
<content type='text'>
previously, the given MotdFile file was read whenever a client
requested it.

Change handling to read the MotdFile contents into memory once
during config file parsing.

Two side effects:
- changes to the MOTD file do not have any effect until ngircds
  configuration is reloaded
- MOTD file does no longer have to reside in the chroot directory
  (the MOTD contents will then not be re-read on reload in that case)
</content>
</entry>
<entry>
<title>New configuration option "NoPAM" to disable PAM</title>
<updated>2010-07-13T14:47:01+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2010-07-13T13:10:35+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=f369177617a0f54e34a1af6fa44d1d1e3f953aeb'/>
<id>urn:sha1:f369177617a0f54e34a1af6fa44d1d1e3f953aeb</id>
<content type='text'>
When the "NoPAM" configuration option is set and ngIRCd is compiled
with support for PAM, ngIRCd will not call any PAM functions: all
connection attemps without password will succeed instead and all
connection attemps with password will fail.

If ngIRCd is compiled without PAM support, this option is a dummy
option and nothing changes: the global server password will still be
in effect.
</content>
</entry>
<entry>
<title>Don't use port 6668 as example for both "Ports" and "SSLPorts"</title>
<updated>2010-03-16T15:16:03+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2010-03-16T15:16:03+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=cbe41ec87506003e484a85301b3c0a6e05bf0ad7'/>
<id>urn:sha1:cbe41ec87506003e484a85301b3c0a6e05bf0ad7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Implement WEBIRC command</title>
<updated>2010-02-10T23:01:53+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2010-02-10T23:01:53+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=6e8cf51bb216f956e7a6fdb5c61b0f2799bf8d2d'/>
<id>urn:sha1:6e8cf51bb216f956e7a6fdb5c61b0f2799bf8d2d</id>
<content type='text'>
The WEBIRC command is used by some Web-to-IRC gateways to set the correct
user name and host name of users instead of their own.

Syntax: WEBIRC &lt;password&gt; &lt;username&gt; &lt;hostname&gt; &lt;ip-address&gt;

The &lt;password&gt; must be set using the new configuration variable "WebircPassword" in the [Global] section of ngircd.conf.

Please note that the &lt;ip-address&gt; is currently not used by ngIRCd (we don't store it in the CLIENT structure, only the resolved hostname).
</content>
</entry>
<entry>
<title>New configuration option "AllowRemoteOper"</title>
<updated>2009-09-30T14:00:04+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2008-04-13T14:39:08+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=f78b0c61e967c66386803a3dc77069c66bd664de'/>
<id>urn:sha1:f78b0c61e967c66386803a3dc77069c66bd664de</id>
<content type='text'>
Added new configuration option "AllowRemoteOper" to control whether
remote IRC operators are allowed to use administrative commands that
affect this server or not

This commit introduces the configuration variable, but actually no
function is using it. That's up for the next patches to come ...
</content>
</entry>
<entry>
<title>Support individual channel keys for pre-defined channels.</title>
<updated>2009-01-20T16:20:30+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2009-01-01T21:26:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=c5000694d16da0a205e7dde49681d589d552d144'/>
<id>urn:sha1:c5000694d16da0a205e7dde49681d589d552d144</id>
<content type='text'>
This patch introduces the new configuration variable "KeyFile" for
[Channel] sections in ngircd.conf. Here a file can be configured for each
pre-defined channel which contains individual channel keys for different
users. This file is line-based and must have the following syntax:

  &lt;user&gt;:&lt;nick&gt;:&lt;key&gt;

&lt;user&gt; and &lt;nick&gt; can contain the wildcard character "*".

Please not that these channel keys are only in effect, when the channel
has a regular key set using channel mode "k"!
</content>
</entry>
<entry>
<title>Fix spelling in some documents.</title>
<updated>2009-01-01T16:56:42+00:00</updated>
<author>
<name>Alexander Barton</name>
<email>alex@barton.de</email>
</author>
<published>2009-01-01T16:56:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.nakidai.ru/ngircd/commit/?id=fd9266df78e32104af3fa72eb5528b5615a2030e'/>
<id>urn:sha1:fd9266df78e32104af3fa72eb5528b5615a2030e</id>
<content type='text'>
</content>
</entry>
</feed>
