On Thu, Apr 14, 2016 at 04:19:06PM +0200, Matěj Cepl wrote:
> On 2016-04-14, 10:26 GMT, Adrian Reber wrote:
> > In the configuration I am running jabberd2 on Fedora I did not
> > have many (maybe any) upgrading the last few versions. EPEL-7
> > would be an upgrade from 2.3.2 to 2.3.6. It probabl
On 2016-04-14, 10:26 GMT, Adrian Reber wrote:
> In the configuration I am running jabberd2 on Fedora I did not
> have many (maybe any) upgrading the last few versions. EPEL-7
> would be an upgrade from 2.3.2 to 2.3.6. It probably depends
> on the installation and which backends are used if the
On 2016-04-14, 10:38 GMT, Tomasz Sterna wrote:
> W dniu 14.04.2016, czw o godzinie 10∶49 +0200, użytkownik Matěj Cepl
> napisał:
>> Do we know what is the upgrade story? Does the latest jabberd2
>> just takes over the original configuration?
>
> Upgrade path is documented:
> https://github.com/jab
W dniu 13.04.2016, śro o godzinie 09∶19 -0700, użytkownik John Oliver
napisał:
> 2) Can jabberd2 authenticate against LDAP?
Yes it can.
Use authreg_ldap or authreg_ldapfull backend.
> 3) Can jabberd2 have users auto-join or automatically be buddies?
Kind of...
storage_ldapvcard module pulls ros
W dniu 14.04.2016, czw o godzinie 10∶49 +0200, użytkownik Matěj Cepl
napisał:
> Do we know what is the upgrade story? Does the latest jabberd2
> just takes over the original configuration?
Upgrade path is documented:
https://github.com/jabberd2/jabberd2/blob/master/NEWS
--
/o__
(_<^' Some pe
On Thu, Apr 14, 2016 at 10:49:30AM +0200, Matěj Cepl wrote:
> On 2016-04-14, 06:27 GMT, Adrian Reber wrote:
> > On Wed, Apr 13, 2016 at 09:19:45AM -0700, John Oliver wrote:
> >> 1) Is this project the 'jabberd' that's available in EPEL?
> >
> > I can answer that one. jabberd in EPEL is jabberd2. As
On 2016-04-14, 06:27 GMT, Adrian Reber wrote:
> On Wed, Apr 13, 2016 at 09:19:45AM -0700, John Oliver wrote:
>> 1) Is this project the 'jabberd' that's available in EPEL?
>
> I can answer that one. jabberd in EPEL is jabberd2. As it is EPEL it
> will not see as many updates as the upstream package
On Wed, Apr 13, 2016 at 09:19:45AM -0700, John Oliver wrote:
> 1) Is this project the 'jabberd' that's available in EPEL?
I can answer that one. jabberd in EPEL is jabberd2. As it is EPEL it
will not see as many updates as the upstream package
Adrian
"I always find this annotation as misleading. It tightens the current
habbit of tightly binding services with servers."
Yeah, that's the main thing about it that bothered me. The standards
seem to encourage the use of sub-domains for naming services. The
examples in XEP-0030 place each service on
Dnia 2011-01-31, pon o godzinie 23:23 -0800, Keith Jay Gillis pisze:
> A host that offers text-based conferencing capabilities; often but not
> necessarily a sub-domain of a Jabber server (e.g.,
> conference.jabber.org).
I always find this annotation as misleading.
It tightens the current habbit
Hi Keith,
I did some investigations on this topic last year. As far as I see it is
not possible without rewriting the sm-component to pass some iq-stanzas
to its clients.
My approach was to write a component that binds to a dummy-domain and
simulates a c2s-connection (e.g. the component starts a
11 matches
Mail list logo
