Re: ircd-ratbox-3.0.0beta1 released

Hi,

Building libratbox without OpenSSL causes errors when you try to link
the ircd binary. The attached patch fixes those errors.

  - nenolod

Hi,

Building libratbox without OpenSSL causes errors when you try to link
the ircd binary. The attached patch fixes those errors.

  - nenolod

Re: ircd-ratbox-3.0.0beta1 released

On Tue, 1 Apr 2008, William Pitcock wrote:

> Hi,
>
> Building libratbox without OpenSSL causes errors when you try to link
> the ircd binary. The attached patch fixes those errors.

I've committed a slightly different variant of this patch.

-Aaron

ircd-ratbox-3.0.0beta2 released

http://www.ircd-ratbox.org/download/testing/ircd-ratbox-3.0.0beta2.tar.bz2
Sig: http://www.ircd-ratbox.org/download/testing/ircd-ratbox-3.0.0beta2.tar.bz2.asc
sha1sum: be1e7d57e0a64ce791e236c47d92360fd5ae9c26

This is the current version of the 'testing' tree of ircd-ratbox.

If you are upgrading from 2.2, you must read doc/whats-new-3.0.txt
If you are upgrading from 2.1, you must read doc/whats-new-2.2.txt
If you are upgrading from 2.0, you must also read doc/whats-new-2.1.txt
If you are upgrading from 1.x, you must also read doc/whats-new-2.0.txt

-- ircd-ratbox-3.0beta2
honor global_cidr setting
fix a bug in bantool that improperly parsed X-lines with spaces them
fix user <at> host spoofs
fix default maxclients to work correctly
fix libratbox build with openssl disabled
don't spin on openssl accepts when there is no data

-- ircd-ratbox-3.0beta1
No release notes, see doc/whats-new-3.0.txt

$Id: RELNOTES 25209 2008-04-09 18:24:36Z androsyn $

ratbox-services chanserv lax on flags.

Hey,

I'm tweaking ircd-ratbox and ratbox-services etc, and find that when I
restart both (ircd-ratbox + ratbox-services), chanserv neglects to
apply modes, for example +i #operators.

This means that after a restart, channels are unmanaged until a
registered (channel) op jumps in, and sets the modes, which are then
enforced.

Why does it not seem to obey CREATEMODES, or have I misunderstood them?

Thanks

Chris

[chris <at> amnesiac]~% uname -a
FreeBSD amnesiac.bayofrum.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Tue
Apr 15 18:40:15 BST 2008     root <at> :/usr/obj/usr/src/sys/AMNESIAC  i386
[chris <at> amnesiac]~% pkg_info | grep ratbox
ircd-ratbox-2.2.8   An advanced, stable IRC daemon, used on many EFnet servers
ratbox-services-1.1.2_2 A highly configurable services package for use
with ircd-ra

--

-- 
One of the main causes of the fall of the Roman Empire was that,
lacking zero, they had no way to indicate successful termination of
their C Programs. (Robert Firth)

R< $&h ! > $- ! $+	$ <at>  $2 <  <at>  $1 .UUCP. > (sendmail.cf)

Re: ratbox-services chanserv lax on flags.

On Sun, Apr 20, 2008 at 11:39:01PM +0100, Chris Rees wrote:
> I'm tweaking ircd-ratbox and ratbox-services etc, and find that when I
> restart both (ircd-ratbox + ratbox-services), chanserv neglects to
> apply modes, for example +i #operators.
> 
> This means that after a restart, channels are unmanaged until a
> registered (channel) op jumps in, and sets the modes, which are then
> enforced.
> 
> Why does it not seem to obey CREATEMODES, or have I misunderstood them?

CREATEMODES is only used if chanserv is supposed to be in the channel
generally (i.e. AUTOJOIN is on), or it is forced to join the channel for
some other reason (i.e. to ban/kick or deop the only user in the channel,
when a ban matches, or RESTRICTOPS/NOOPS are on respectively).

There is a further conf option to chanserv called "autojoin_empty", which
controls whether chanserv will create channels marked as AUTOJOIN.  The
default to this is off -- as being enabled tends to result in lots of
channels that have noone but chanserv in them.

It would appear that autojoin_empty is missing from the example.conf though.

If a mode is to be enforced, ENFORCEMODES should be used..

Cheers,

--

-- 
-                 Lee H // anfl
-        I code, therefore I break things.

Re: ratbox-services chanserv lax on flags.

On Mon, Apr 21, 2008 at 09:10:52PM +0100, Lee H wrote:
> On Sun, Apr 20, 2008 at 11:39:01PM +0100, Chris Rees wrote:
> > I'm tweaking ircd-ratbox and ratbox-services etc, and find that when I
> > restart both (ircd-ratbox + ratbox-services), chanserv neglects to
> > apply modes, for example +i #operators.

> > This means that after a restart, channels are unmanaged until a
> > registered (channel) op jumps in, and sets the modes, which are then
> > enforced.

> > Why does it not seem to obey CREATEMODES, or have I misunderstood them?

> CREATEMODES is only used if chanserv is supposed to be in the channel
> generally (i.e. AUTOJOIN is on), or it is forced to join the channel for
> some other reason (i.e. to ban/kick or deop the only user in the channel,
> when a ban matches, or RESTRICTOPS/NOOPS are on respectively).

In fact, CREATEMODES is only used if chanserv is creating the channel or
lowering TS, both of which only happen if AUTOJOIN is on.

Note that if ENFORCEMODES is set, it is used and CREATEMODES is ignored;
a case could be made to OR them in that case, allowing for some modes to
be set by default but alterable by any chanop while forcing other modes
on at all times.

> There is a further conf option to chanserv called "autojoin_empty", which
> controls whether chanserv will create channels marked as AUTOJOIN.  The
> default to this is off -- as being enabled tends to result in lots of
> channels that have noone but chanserv in them.

ircd-ratbox-3.0.0beta3 released

http://www.ircd-ratbox.org/download/testing/ircd-ratbox-3.0.0beta3.tar.bz2
Sig: http://www.ircd-ratbox.org/download/testing/ircd-ratbox-3.0.0beta3.tar.bz2.asc
sha1sum: cfde980413696bd99f47633f56b4ca934a5e15b4

This is the current version of the 'testing' tree of ircd-ratbox.

If you are upgrading from 2.2, you must read doc/whats-new-3.0.txt
If you are upgrading from 2.1, you must read doc/whats-new-2.2.txt
If you are upgrading from 2.0, you must also read doc/whats-new-2.1.txt
If you are upgrading from 1.x, you must also read doc/whats-new-2.0.txt

-- ircd-ratbox-3.0.0beta3
fix an issue with CAP END releasing clients before it should
report bandb errors in a useful fashion
strip tabs when reading from help/motd etc
override default_max_clients if it is == 0
fix ssl issue with wanting reads/writes
fix some cases where /list can freeze a client
stop libltdl from installing an empty include directory
improve SIGCHLD handling in the ircd

-- ircd-ratbox-3.0.0beta2
honor global_cidr setting
fix a bug in bantool that improperly parsed X-lines with spaces them
fix user <at> host spoofs
fix default maxclients to work correctly
fix libratbox build with openssl disabled
don't spin on openssl accepts when there is no data