Displaying 12 results from an estimated 12 matches for "kule".
Did you mean:
rule
2006 Jan 17
1
Newbie question on using friedman.test()
...;9", "10", "11", "12", "13",
"14", "15", "16", "17", "18", "19", "20", "21", "22", "23", "24"
), class = "data.frame")
========
Bill Kules
Principal, Takoma Software, Inc., Takoma Park, MD
www.takomasoftware.com
Ph.D. Candidate, University of Maryland Human-Computer Interaction Lab
www.cs.umd.edu/hcil
wmk at takomasoftware.com
(301) 405-2725 voice
(301) 891-7271 voice + voicemail
(301) 891-7273 fax
(301) 755-7982 mobile
========
2020 Feb 03
3
Ldapsearch against Samba AD returns records outside the search base
On Mon, 2020-02-03 at 18:17 +0200, Palle Kuling via samba wrote:
> Hello,
>
> I did some detective work here, stepping through all the versions
> from
> the old 4.9.4 database onwards, building them from source on an
> isolated
> system and doing ldapsearch against them. It is the change from
> 4.10.13
> to 4.11.0 (or maybe in general from pre-4.11 to 4.11?) that
2020 Feb 06
1
Ldapsearch against Samba AD returns records outside the search base
On Thu, 2020-02-06 at 16:21 +0200, Palle Kuling via samba wrote:
> Hello,
>
> I did a git bisect between 4.10.0rc1 and 4.11.0. The result is as
> follows:
> b6b5b5fe355fee2a4096e9214831cb88c7a2a4c6 is the first bad commit
> Date: Wed Mar 6 15:28:45 2019 +1300
>
> lib ldb key value: fix index buffering
>
> Is there anything else I should check?
Thanks, that
2020 Feb 01
3
Ldapsearch against Samba AD returns records outside the search base
On Fri, 2020-01-31 at 15:50 +0200, Palle Kuling via samba wrote:
> Hi,
>
> I noticed the following problem with records returned outside the search
> base when the query is run against a Samba DC, but when the same query
> is run against a Windows 2008 or 2012 DC it does not happen. I'm pretty
> sure it worked correctly in the past. I updated from Samba 4.9.4 to
>
2020 Feb 01
2
Ldapsearch against Samba AD returns records outside the search base
On Sat, 2020-02-01 at 17:22 +0000, Rowland penny via samba wrote:
> On 01/02/2020 16:29, Palle Kuling via samba wrote:
> >
> > Queried against Samba 4.11.4 (query is for OU=Business but response is
> > from OU=Test):
> > $ldapsearch -D username at internal.xxx.yy -w password -H
> > ldaps://192.168.1.1 -s one -b ou=business,dc=internal,dc=xxx,dc=yy
> >
2020 Feb 01
2
Ldapsearch against Samba AD returns records outside the search base
Hello,
Is it not Samba that is listening to the LDAP ports and is serving me
the answer to my query? This problem does not only happen when the LDAP
database is searched using ldapsearch, it happens also using other tools
that connect to the LDAP ports. I still don't fully grasp what this has
to do with the uniqueness of the sAMAccountNames - they are unique
throughout my directory and I
2020 Feb 01
2
Ldapsearch against Samba AD returns records outside the search base
Hello,
Ldbsearch returns the correct result. However this particular query is
performed by an external system (that does not have access to the LDB
files), to check whether a certain user belongs to a specific OU or not.
The query is performed over LDAP against Samba, so it is not a
ldapsearch-only problem. I only used ldapsearch to verify the behavior.
Regardless of if the query is wrong or
2020 Feb 01
0
Ldapsearch against Samba AD returns records outside the search base
On 01/02/2020 09:54, Palle Kuling via samba wrote:
> Hello,
>
> Ldbsearch returns the correct result. However this particular query is
> performed by an external system (that does not have access to the LDB
> files), to check whether a certain user belongs to a specific OU or
> not. The query is performed over LDAP against Samba, so it is not a
> ldapsearch-only problem. I
2020 Feb 02
0
Ldapsearch against Samba AD returns records outside the search base
Hello all,
I just tried this on our setup and it ist the same there. I get results
from other OUs. Using sub instead of one I get the "right" results.
Regards
Christian
Am 01.02.20 um 20:26 schrieb Andrew Bartlett via samba:
> On Sat, 2020-02-01 at 17:22 +0000, Rowland penny via samba wrote:
>> On 01/02/2020 16:29, Palle Kuling via samba wrote:
>>>
>>>
2020 Feb 01
0
Ldapsearch against Samba AD returns records outside the search base
On 01/02/2020 16:29, Palle Kuling via samba wrote:
>
>
> Queried against Samba 4.11.4 (query is for OU=Business but response is
> from OU=Test):
> $ldapsearch -D username at internal.xxx.yy -w password -H
> ldaps://192.168.1.1 -s one -b ou=business,dc=internal,dc=xxx,dc=yy
> "(&(objectCategory=person)(objectClass=user)(sAMAccountName=testadmin))"
> #
2020 Feb 06
0
Ldapsearch against Samba AD returns records outside the search base
Hello,
I did a git bisect between 4.10.0rc1 and 4.11.0. The result is as
follows:
b6b5b5fe355fee2a4096e9214831cb88c7a2a4c6 is the first bad commit
Date: Wed Mar 6 15:28:45 2019 +1300
lib ldb key value: fix index buffering
Is there anything else I should check?
Regards,
-P
On 2020-02-04 00:08, Andrew Bartlett via samba wrote:
> On Mon, 2020-02-03 at 18:17 +0200, Palle Kuling via
2020 Feb 03
0
Ldapsearch against Samba AD returns records outside the search base
Hello,
I did some detective work here, stepping through all the versions from
the old 4.9.4 database onwards, building them from source on an isolated
system and doing ldapsearch against them. It is the change from 4.10.13
to 4.11.0 (or maybe in general from pre-4.11 to 4.11?) that breaks it;
after that the onelevel scope is not applied correctly.
Ldbsearch also returns wrong results when