Package: dancer-services
Version: 1.8.0.6.3-2.1
With the following (pretty minimal) dancer-ircd
configuration:
---
# Name and description of server.
M:irc.mysociety.org.:0.0.0.0:mySociety IRC:
# Location, email and description of admins.
A:Here, there and everywhere:[EMAIL PROTECTED]:mySociety team <[EMAIL
PROTECTED]>
# Classes of connections. Fields are class number, ping frequency, connect
# frequency (for servers) or number of permitted connections per IP (for
# clients), maximum number of links (?) and send queue size.
# Class for users
Y:1:90:0:100:10000
# One for servers
Y:2:90:300:10:100000
# Permission for clients to connect.
# Fields are ident, password, host, ? and class number.
I:NOMATCH::*::1
# Permit services to connect.
C:localhost:M!Kdqa.m:services.:2
N:localhost:$1$WC47s25A$Wk.Gx29uv7Rwz2rB1CAek0:services.:2
# Ports to listen on.
P::::6667
P::::9219
---
and the following /etc/dancer-services/services.conf
---
# Name and email of admins.
A:mySociety team <[EMAIL PROTECTED]>
# Name of server we pretend to be.
N:services.:Local services
# IRC server to which we connect (there needs to be a corresponding N: line in
# the server config).
S:M!Kdqa.m:localhost:6667
# Administrators of the services.
O:*:$1$f05.elnC$ZBa/fy6wKPdNy7Y4Gm6c4.:chris:s
---
dancer-services crashes with SIGSEGV soon after connecting
if there are users on the server, or immediately when a
user connects.
The crash occurs in server.c at line 918:
if (ircncmp(Me.name, lptr->server->name, strlen(lptr->server->name))) {
because lptr->server is NULL. On closer investigation this
seems to be because when the ircd connects to services, it
supplies `*.org' as its server name; this confuses
dancer-services, and because it doesn't bother to check
whether lptr->server is non-NULL it crashes when it does
the compare above.
Presumably there's some change I could make to the
configuration which would prevent this, though it's not
obvious to me from my reading of the code and docs.
Any suggestions would be appreciated! Also,
dancer-services probably oughtn't to crash in this case.
--
Chris Lightfoot
mySociety
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
