Re: releases plans

[Stephen Mahood]

Chris,

I know from the debian package page that they are looking for a new
maintainer...I am not familiar enough on how to maintain a site, but
woudl you be interested in maintaining it?
http://packages.debian.org/unstable/main/jabberd2

It is being considered for deployment with mayfirst.org but preference
is for the package to be in the debian repos

Stephen

On 03/21/2012 04:34 PM, Christian Franke wrote:
 On 03/21/2012 04:33 PM, Stephen Mahood wrote:
 I am new to the community but wondering if the release would be
 supported in the debian repos as well? Last one i see is in sid and is
 2.2.8-2.2

 Thanks :)
 
 I happen to use jabberd2 on an amd64 machine running Debian Wheezy.
 Therefore, I have built debian packages for jabberd2 and its
 dependencies for that specific target.
 
 These packages are publicly available at [1], however it should be noted
 that this is currently a repo where I store my packages - while I try
 to provide tested packages of a certain quality, it may happen that
 packages do not work as intended, are not available for a certain
 platform or are outdated.
 
 Best Regards,
 Christian Franke
 
 [1] http://nowhere.ws/dn42/debian/pool/wheezy/main/
 
 

Re: Add users and multi mysql

[Stephen Mahood]

Would this support a sasl with Channel Binding? (I will admit I am not
entirely familiar with channel binding)

On 03/21/2012 04:17 PM, Tomasz Sterna wrote:
 Dnia 2012-03-21, śro o godzinie 10:38 -0600, Stephen Mahood pisze:
 a central server to run the software, but
 to have multiple VPN having the ability to create jabber accounts
 specific to their address (virtual hosting) but the other thing we
 want to restrict the creating of accounts to the local mysql for the
 virtual hosted site. Is that feasible with jabberd2.x? 
 
 Of course it is. It always was. :-)
 
 What you need is to:
 1. configure several domains in c2s.xml - local/id sections
 2. configure sm.xml for every domain and launch sm instance
 
 At least how it is used to be.
 Since 2.1.16 you don't have to do 1, as you may configure one default
 local/id entry in c2s.xml[1], which will be used if there is no specific
 id for a domain.
 Since 2.2.9 jabberd2 is able to support many domains in one SM process,
 so you may run just one sm instance holding all your domains, similarly
 by configuring several local/id sections in sm.xml[2].
 
 To lock account creation, setup local/id section in c2s.xml to not
 include register-enable attribute. You will then need to create the
 users manually in DB.
 See section 5.5 of the InstallGuide[3].
 It may be feasible to add password-change attribute then, to allow
 existing users to change password.
 
 P.S. If anyone volunteers to fix the documentation, I will be more than
 happy. :-)
 [1] https://github.com/Jabberd2/jabberd2/blob/master/etc/c2s.xml.dist.in
 [2] https://github.com/Jabberd2/jabberd2/blob/master/etc/sm.xml.dist.in
 [3] 
 https://github.com/Jabberd2/jabberd2/wiki/InstallGuide-CommonConfigurationTasks