Dnia 2012-12-13, czw o godzinie 18:42 +0100, Guido Winkelmann pisze:
> The first patch had a memory leak.
>
> Am Mittwoch, 12. Dezember 2012, 17:07:34 schrieb Guido Winkelmann:
> > This patch appears to work. Note, I have only done superficial testing
> > (checked that I can log in as a user who i
The first patch had a memory leak.
Am Mittwoch, 12. Dezember 2012, 17:07:34 schrieb Guido Winkelmann:
> This patch appears to work. Note, I have only done superficial testing
> (checked that I can log in as a user who is in the specified group and that
> I can not log in as one that is not in this
Ah, nobody use that yet, please. I just realized I forgot some ldap_memfree()
calls in _ldapfull_check_password(), so this will probably leak memory...
Am Donnerstag, 13. Dezember 2012, 14:47:12 schrieb Guido Winkelmann:
> The same patch for git master.
Am Mittwoch, 12. Dezember 2012, 09:40:49 schrieb Justin T Pryzby:
> I compared the two ldap modules here:
> http://www.mail-archive.com/jabberd2@lists.xiaoka.com/msg01381.html
> (Was it really three years ago??)
>
> Is there any reason to maintain both? What does "full" mean in
> ldapfull?
At a
The same patch for git master.>From 559475a60dbe5a793f2632f5abb723ec19bedc07 Mon Sep 17 00:00:00 2001
From: Guido Winkelmann
Date: Thu, 13 Dec 2012 00:57:10 +0100
Subject: [PATCH] ldapfull: Check for ldap group membership on login
Administrators can now supply a configuration directive. If
it is
Dnia 2012-12-12, śro o godzinie 09:40 -0700, Justin T Pryzby pisze:
> Is there any reason to maintain both?
Not really. The lack of knowledge of LDAP prevented me from merging
these, but I didn't want to reject this usefull user submition, so I
merged it as-is.
If anyone is willing to make effort
I compared the two ldap modules here:
http://www.mail-archive.com/jabberd2@lists.xiaoka.com/msg01381.html
(Was it really three years ago??)
Is there any reason to maintain both? What does "full" mean in
ldapfull?
Justin
On Wed, Dec 12, 2012 at 05:07:34PM +0100, Guido Winkelmann wrote:
> This pa
This patch appears to work. Note, I have only done superficial testing
(checked that I can log in as a user who is in the specified group and that I
can not log in as one that is not in this group). I have not tested this
against AD, only OpenLDAP.
This patch applies to 2.2.17, but not to git-m
Am Dienstag, 11. Dezember 2012, 18:12:42 schrieb Guido Winkelmann:
> Am Dienstag, 11. Dezember 2012, 17:50:03 schrieb Tomasz Sterna:
> > Dnia 2012-12-11, wto o godzinie 17:11 +0100, Guido Winkelmann pisze:
> > > For the services I have running so far, I was able to implement this
> > > by creating
Am Dienstag, 11. Dezember 2012, 11:43:49 schrieb Eric V. Smith:
> On 12/11/2012 11:11 AM, Guido Winkelmann wrote:
> > Hi,
> >
> > I'm trying to integrate Jabberd2 into my single-account scheme using LDAP,
> > and I'm running into problems with that.
> >
> > One of my requirements for this is that
Am Dienstag, 11. Dezember 2012, 17:50:03 schrieb Tomasz Sterna:
> Dnia 2012-12-11, wto o godzinie 17:11 +0100, Guido Winkelmann pisze:
> > For the services I have running so far, I was able to implement this
> > by creating a new LDAP group (with objectClass: groupOfNames) for each
> > service and
Dnia 2012-12-11, wto o godzinie 17:11 +0100, Guido Winkelmann pisze:
> For the services I have running so far, I was able to implement this
> by creating a new LDAP group (with objectClass: groupOfNames) for each
> service and having every service check whether a freshly authenticated
> user is a m
On 12/11/2012 11:11 AM, Guido Winkelmann wrote:
> Hi,
>
> I'm trying to integrate Jabberd2 into my single-account scheme using LDAP,
> and
> I'm running into problems with that.
>
> One of my requirements for this is that I need to be able to specify for
> every
> user exactly which services
Hi,
I'm trying to integrate Jabberd2 into my single-account scheme using LDAP, and
I'm running into problems with that.
One of my requirements for this is that I need to be able to specify for every
user exactly which services he or she is allowed to access, so that, for
example, a user who on
14 matches
Mail list logo
