Jabber module only accepts ports 5220-5229

[anonymous]

Since I'm behind a very restrictive firwall, I use jabber80.com, but bitlbee limits the port used by jabber.

It would be nice if this restriction cuold be removed or at least switched through an option.

[Jelmer Vernooij]

I think that should be a switch. You don't want people on public servers to be able to connect to a random port on a random server.

[wilmer]

Yeah, maybe it would make sense to make a system-wide flag to disable paranoid stuff like this all at once (although this is the only thing I can think of right now). Of course it shouldn't be a per-user setting, that would make the whole check completely useless. :-)

[wilmer]

Oh, and disabling this check should be pretty easy, see protocols/jabber/jabber.h (IIRC) to change the allowed range or just disable the check, IIRC in jabber.c.

[wilmer]

Postponing this just a little bit. I need some way to set global (for all IM modules) limits/capabilities that make it easier to configure what should be allowed or not (also think of file transfers) and don't want to do that in 1.2 already.

[wilmer]

Partially fixed: Not using a simple port range anymore, but a port list, and I added 80 and 443.

changeset:devel,388

[Dima]

Bitlbee pwns, ownz, owns, pwnz, 0wnz3rz and pwnz3rz.It's also very handy! I've been using it about a year now combined with ssh, seecrn, irssi and dyndns it really comes into its own. You can feel at home on any net connected machine in the world