Re: Possible transaction issue with LMDB

2018-08-17 Thread William Brown
On Fri, 2018-08-17 at 07:06 +0100, Howard Chu wrote: > > I'm quite aware that it is COW - this issue is specific to COW > > trees. > > Transactions must be removed in order, they can not be removed out > > of > > order. It is about how pages are reclaimed for the freelist > > Incorrect. We may

Re: Possible transaction issue with LMDB

2018-08-16 Thread William Brown
when node lifetimes expire. I hope that this explains the issue more thoroughly. > Regards, > Leonid. > > > 2018-08-16 13:03 GMT+03:00 William Brown : > > Hi there, > > > > While doing some integration testing of LMDB I noticed that there > > may > >

Possible transaction issue with LMDB

2018-08-16 Thread William Brown
Hi there, While doing some integration testing of LMDB I noticed that there may be an issue with out of order transaction handling. The scenario is: Open Read TXN A Open Write TXN X, and change values of the DB Commit X Open Read TXN B Open Write TXN Y, and change values of the DB Commit Y Open

MDB questions

2018-05-07 Thread William Brown
Hi there, I have a few questions about MDB, and I have some things I'd like to work on. In the docs there are a few references that reference binary searching. It's not 100% clear but I assume this is a binary search of the keys in a BTree node, not that MDB is a bst. How does MDB provide

Re: IETF opinion change on "implicit TLS" vs. StartTLS

2018-02-16 Thread William Brown
On Mon, 2018-02-12 at 18:10 -0800, Quanah Gibson-Mount wrote: > --On Tuesday, February 13, 2018 9:31 AM +1000 William Brown > <wibr...@redhat.com> wrote: > > > On Mon, 2018-02-12 at 14:30 +0100, Michael Ströder wrote: > > > HI! > > > > > > To me

Re: IETF opinion change on "implicit TLS" vs. StartTLS

2018-02-12 Thread William Brown
ecated. Rather it should be > recommended and the _optional_ use of StartTLS should be strongly > discouraged. Yes, I strongly agree with this. I have evidence to this fact and can provide it if required, > > Ciao, Michael. > -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

Re: Antw: Re: ssf Security Question

2017-11-21 Thread William Brown
it too, but it was a pretty silent change - even we didn't know it was coming. PS: Again full disclosure for clarity, I work on RHDS. -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

Re: ssf Security Question

2017-11-20 Thread William Brown
On Mon, 2017-11-20 at 11:22 +, Howard Chu wrote: > William Brown wrote: > > On Fri, 2017-11-17 at 08:34 +0100, Michael Ströder wrote: > > > William Brown wrote: > > > > Just want to point out there are some security risks with ssf > > > > sett

Re: One account for modifying directory and wiki

2017-11-20 Thread William Brown
On Fri, 2017-11-17 at 07:46 -0500, John Lewis wrote: > On Fri, 2017-11-17 at 12:51 +1000, William Brown wrote: > > On Thu, 2017-11-16 at 11:26 -0500, John Lewis wrote: > > > I want to have one account for modifying both a LDAP directory > > > and > > > a > &

Re: ssf Security Question

2017-11-19 Thread William Brown
On Fri, 2017-11-17 at 08:34 +0100, Michael Ströder wrote: > William Brown wrote: > > Just want to point out there are some security risks with ssf > > settings. > > I have documented these here: > > > > https://fy.blackhats.net.au/blog/html/2016/11/23/the_minssf

Re: Is existing documentation kind of vague?

2017-11-16 Thread William Brown
an informed opinion. As mentioned, I'm not here to throw insults and criticisms, I'm here to have positive, respectful discussions about technology, to provide different ideas, and to learn from others :) Thanks, > > On Fri, Nov 17, 2017 at 4:49 AM, William Brown <wibr...@redhat.com>

Re: ssf Security Question

2017-11-16 Thread William Brown
On Thu, 2017-11-16 at 21:25 -0800, Quanah Gibson-Mount wrote: > --On Friday, November 17, 2017 12:53 PM +1000 William Brown  > <wibr...@redhat.com> wrote: > > Hi William, > > > Hey mate, > > > > Just want to point out there are some security risks with

Re: ssf Security Question

2017-11-16 Thread William Brown
ve material. I would advise that you use LDAPS with TLS instead, or provide suitable access control over your network segments to prevent these issues. Relying on SSF can allow data leaks from misconfigured clients. Hope that helps, -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

Re: One account for modifying directory and wiki

2017-11-16 Thread William Brown
ks (binds) and then use groups to provide authorization control as to "who" can access the wiki. I hope that helps you, > -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

Re: Is existing documentation kind of vague?

2017-11-16 Thread William Brown
e original poster > > mentioned by pointing to > > http://www.rexconsulting.net/ldap-protocol-uidNumber.html > > > > 2. MOD_INCREMENT with pre-read control > > > > Of course none of the solutions work when hitting multiple > > providers > > hard i

Re: restrict wildcard searches

2017-11-16 Thread William Brown
end. > > 2. It disables sub-string matching on 'mail' completely. You might > solve > this by building a partial replica or a LDAP proxy dedicated to the > exact search on known e-mail addresses. > > AFAICS other possibilities would be implementing an overlay or a > dynacl > module for your specific needs. > > Ciao, Michael. > -- Sincerely, William Brown Software Engineer Red Hat, Australia/Brisbane

Re: Load testing bind performance

2017-11-02 Thread William Brown
On Thu, 2017-11-02 at 09:08 +0100, Michael Ströder wrote: > William Brown wrote: > > On Wed, 2017-11-01 at 20:33 +0100, Michael Ströder wrote: > > > Tim wrote: > > > > I've used the python-ldap library to simulate other varieties > > > > of > >