gmane.network.irc.ircd-ratbox.user

Re: ircd-ratbox-3.0.8-unicode1

Jilles Tjoelker — 2013-05-19T22:45:55


Note that the matching used for channel bans does not support any kind
of escape character. A '*' or '?' in a ban mask is always special.

So the current approach of allowing them is only good if you think
nickname-based bans are silly anyway.

Re: ircd-ratbox serve tweaks

Daniel Corbe — 2013-05-15T06:24:56

Jason Booth <metzenw< at >gmail.com> writes:


Try adding the flood_exempt flag to the auth block for any users you
want to remove flood control for. 

-Daniel

ircd-ratbox serve tweaks

Jason Booth — 2013-05-14T22:48:54

Greetings,

 I have a general question about speed tweaks. I have noticed that on
my internal ratbox server if a user puts in 1 <return>,2 <return>,3
<return>,4 <return>,5  <return> that there is a ~2  second delay on the 5th
entry. This appears to be a throttling issue. I set default_floodcount to
100 to see if this would help but the issue has not gone away. Can anyone
tell me why there is a slow down in the chat after the 4th message? Many
thanks in advance.

My configuration

http://pastebin.com/KvTr9T9e

ircd-ratbox-3.0.8

Regards,

-J

Re: ircd-ratbox-3.0.8-unicode1

Daniel Corbe — 2013-05-06T05:37:47


It's a misnomer because the server doesn't (and shouldn't) care about
the encoding being used.  It's called -unicode because the intent is to
do the minimum amount of work possible to support UTF-8 on the client.

Most clients are either capable of some sort of auto-detection of UTF-8
or explicitly require the user to set the encoding anyways.  

irssi and xchat just sort of work out of the box and most xmpp clients
(remembering that the original intent of this project is to marry Jabber
MUCs to an IRC server) support UTF by default because that's what the
XMPP specification says they need to do.


None of this is really relevant.  Confusion for the sake of lulz may be
annoying but it won't break the server.  In corner cases where this
becomes an issue, it can be dealt with on an individual basis.

-Daniel

Re: ircd-ratbox-3.0.8-unicode1

Jeremy Chadwick — 2013-05-04T17:40:42

The patch just says "Unicode".  Unicode means a lot of different things;
are we talking about UTF-8, UTF-16, or UTF-32?  I have to assume UTF-8
(from briefly examining the patch).

So here's a question for you: what's to stop someone from using a
nickname that contains characters that visually look nearly identical to
delimiters or non-permitted (protocol-violating) characters?  While
these won't break parsers, they will cause mass confusion for end-users.
Examples include, but are not limited to:

- U+0x02f8 -- Raised colon (:)
- U+0xfe30 -- Vertical two-dot (looks like colon) (:)
- U+0xfe55 -- Small colon (:)
- U+0xfe5f -- Small hash symbol (#)
- U+0xfe60 -- Small ampersand (&)
- U+0xfe61 -- Small asterisk (*)
- U+0xfe69 -- Small dollar symbol ($)
- U+0xfe6b -- Small at symbol (< at >)
- U+0xff03 -- (Japanese) Full-width hash symbol (#)
- U+0xff04 -- (Japanese) Full-width dollar symbol ($)
- U+0xff06 -- (Japanese) Full-width ampersand (&)
- U+0xff0a -- (Japanese) Full-width asterisk (*)
- U+0xff1a -- (Japanese

Re: ircd-ratbox-3.0.8-unicode1

Daniel Corbe — 2013-05-04T16:25:36

Jilles Tjoelker <jilles< at >stack.nl> writes:


The proto-breaking characters are disabled in the update version of the
patch.  

I'm not as concerned about glob characters like * and ? though.  The
MUC service will have to interpret the user's wishes when placing a
channel ban from the jabber side.  It's something I'll need to be
cognisant of as I progress with this project.

The IRC users will have to be clever enough to do host bans.  


Jiles,

Thanks for the pointers.  The updated patch is up.

-Daniel

Re: ircd-ratbox-3.0.8-unicode1

Jilles Tjoelker — 2013-05-04T15:36:36





Allowing characters like '#', '$', '&', '*' and ':' breaks the protocol
(this list is not exhaustive). For example, PRIVMSG interprets things
starting with '#' or '&' as channels and things starting with '$' as
globals. The asterisk and question mark are wildcard characters, which
is "fun" for miscreants who will make it likely that everyone will be
banned when an attempt is made to ban them. Parameters starting with a
colon are special to the framing mechanism; clients and servers alike
will get confused when a nickname starts with a colon.

If you want to enable the remaining us-ascii characters (with the
exception of the tilde '~'), you will have to be a bit more clever.

Enabling the bytes 128-255 should pose fewer problems. However, it would
be a good idea to add a check for valid UTF-8 and to truncate at
character boundaries.

ircd-ratbox-3.0.8-unicode1

Daniel Corbe — 2013-05-04T14:43:28

Hi,

As part of an ongoing effort to create a stand-alone Jabber MUC which uses an IRC
server as a back end, I've created a very simple patch to ircd-ratbox
which enables unicode nick support.

As it turns out, it was quite easy because the server is pretty much
agnostic to encoding.

The patch is available at
http://www.corbe.net/static/ircd-ratbox-3.0.8-unicode.patch

A production server is up at irc.corbe.net.

The working repo can be tracked at
git://apollo.corbe.net/ircd-ratbox.git

Cheers.
-Daniel

banserv

Rick Dicaire — 2013-01-27T18:34:04

Hi folks, ratbox-services version 1.2.4, ircd-ratbox 3.0.8.

All the services work, except for banserv.

I set a temp kline with banserv, I can see the kline when querying
banserv, but I cannot see the kline
when I do /stats k. Nor does the kline have any effect.
Test client is not in any exempts.

Nothing in ircd or services logs indicates an error.

ircd shared block:

shared {
oper = "*< at >*", "ratbox.services";
flags = all;
}

I did a /rehash after adding the shared block.
I stopped, started ratbox-services.

Are klines set with banserv supposed to show in /stats k?
Any ideas why the klines set with banserv don't prevent client
matching said kline from
connecting?

I'm at a loss how to further troubleshoot this issue.

Re: Static source code analysis (or fun and profit)

John Smith — 2013-01-09T12:31:18

And here are the results for ratbox-services :

http://lbalbalba.x90x.net/clang-analyzer/ratbox-services/


Regards,


John Smith

Static source code analysis (or fun and profit)

John Smith — 2013-01-01T11:01:21

Hi,


Just for fun, I decided to run the llvm/clang static source code
analyzer (see: http://clang-analyzer.llvm.org/) on ircd-ratbox. For
those interested, the results can be found here :

http://lbalbalba.x90x.net/clang-analyzer/ircd-ratbox/



Regards,


John Smith.

Re: ircd-ratbox-3.0.8 released(urgent securityupdate)

Andrey Andreev — 2013-01-01T02:12:47

Ignore me ... I've tried with /modlist m_capab instead of /modlist m_capab.so.

Quoting Andrey Andreev <narf< at >bofh.bg>:

Re: ircd-ratbox-3.0.8 released(urgent securityupdate)

Andrey Andreev — 2013-01-01T01:33:19

Quoting Jeremy Chadwick <ratbox< at >jdc.parodius.com>:


modlist, naturally.

Re: ircd-ratbox-3.0.8 released(urgent securityupdate)

Jeremy Chadwick — 2013-01-01T01:18:37

Did you determine this by looking at ircd.conf or by doing "/quote
modlist"?  If the former, please do the latter.

Re: ircd-ratbox-3.0.8 released(urgent securityupdate)

Andrey Andreev — 2013-01-01T00:50:28

My ircds don't seem to have that module loaded (I didn't manually  
unload it). I guess it is safe to assume that I'm not vulnerable to  
that bug then?

- Andrey

Quoting androsyn <androsyn< at >ratbox.org>:

Re: ircd-ratbox-3.0.8 released(urgent security update)

Pierre Breau — 2012-12-31T22:25:57

Happy new year 2013 :).

Cheers

Pierre Breau

-----Original Message-----
From: ircd-ratbox [mailto:ircd-ratbox-bounces< at >lists.ratbox.org] On Behalf Of
Jilles Tjoelker
Sent: Monday, December 31, 2012 6:21 PM
To: androsyn
Cc: ircd-ratbox< at >lists.ratbox.org
Subject: Re: [ircd-ratbox] ircd-ratbox-3.0.8 released(urgent security
update)

On Mon, Dec 31, 2012 at 05:01:07PM -0500, androsyn wrote:



If you do this, note that making a new server link will then either fail
entirely or create a link that will not work properly. Caveat emptor.

--
Jilles Tjoelker
_______________________________________________
ircd-ratbox mailing list
ircd-ratbox< at >lists.ratbox.org
http://lists.ratbox.org/cgi-bin/mailman/listinfo/ircd-ratbox

Re: ircd-ratbox-3.0.8 released(urgent security update)

Jilles Tjoelker — 2012-12-31T22:21:25



If you do this, note that making a new server link will then either fail
entirely or create a link that will not work properly. Caveat emptor.

ircd-ratbox-3.0.8 released(urgent security update)

androsyn — 2012-12-31T22:01:07

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Well this is an embarrassing release for certain, turns out there was a
nasty little bug in the CAPAB handling code that allows for a remote
attacker to crash the ircd.  With that said, all admins are urged to
upgrade to ircd-ratbox-3.0.8 immediately.  See the link below for further
details, the link mentions Charybdis but really this impacts all ircd-ratbox
derived ircds.  

http://www.ratbox.org/ASA-2012-12-31.txt

If you happen to be running a vunerable server and for whatever reason
cannot upgrade immediately, a /quote modunload m_capab.so should mitigate
the effects of the bug.

- -Aaron

(now for the standard boiler plate release notice)


http://www.ratbox.org/download/ircd-ratbox-3.0.8.tar.bz2
Sig: http://www.ratbox.org/download/ircd-ratbox-3.0.8.tar.bz2.asc
sha1sum: 544a94032ec700897204acd50ca176539f731b05

Please note as of this release, the 3.0 branch is now marked as 'stable'. 
The 2.2 branch will no longer be maintained.

This is the current releas

Re: operator in irdc.config an channel oprators

Breau, Pierre — 2012-08-23T14:33:44

/msg userserv register username password email
/msg userserv login username password

/msg chanserv register #channel

You might need to set ure sell in the services conf as a oper or something
been a while i dint touch ratbox services and then try olgin on operserv

Pierre Breau
 On Aug 23, 2012 11:26 AM, "Sven Hergenhahn" <svenxy< at >gmx.net> wrote:

Re: operator in irdc.config an channel oprators

Sven Hergenhahn — 2012-08-23T14:26:29

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

Am 23.08.2012 16:12, schrieb Chris Rees:


Nope.

* Insufficient parameters to OPERSERV::OLOGIN

- -OPERSERV- No help is available on ologin

and for < at >pierre

/msg operserv omode #channel +o urenick

- -OPERSERV- No access to OPERSERV::OMODE

Does #wartung need to be registered?

Thanks for your help.

Sven

- -- 
Sven Hergenhahn
Heidelberg.Germany.Earth.

GPG Key 0x0DCE97AB
Fingerprint E452 94A5 A426 1CA5 B321 5A71 D1AE 3696 0DCE 97AB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREKAAYFAlA2PZUACgkQ0a42lg3Ol6sW9gD8CHMqarzlbpJNLqprL9sQThpn
C27PbvyuWcXRHKQWv38A/RVzOZROItIK64oUkr9DxvH2TgPVXMSPXq0KlaIRkxdm
=IMRT
-----END PGP SIGNATURE-----

Re: operator in irdc.config an channel oprators

Breau, Pierre — 2012-08-23T14:21:05

Yes ure right

Pierre Breau
 On Aug 23, 2012 11:19 AM, "Chris Rees" <utisoft< at >gmail.com> wrote: