[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: 2.4.44 + ITS 8432 patch segfault in modify_add_values
- To: Quanah Gibson-Mount <quanah@symas.com>, "Paul B. Henson" <henson@acm.org>
- Subject: Re: 2.4.44 + ITS 8432 patch segfault in modify_add_values
- From: Frank Swasey <Frank.Swasey@uvm.edu>
- Date: Tue, 21 Feb 2017 17:05:26 +0000
- Accept-language: en-US
- Cc: "openldap-technical@openldap.org" <openldap-technical@openldap.org>
- Content-id: <EF32578671367C49BA3A19285EDFCB1E@ad.uvm.edu>
- Content-language: en-US
- In-reply-to: <507D33782D21B69B197902F8@[192.168.1.30]>
- References: <20170215012451.GB3387@bender.cpp.edu> <WM!998e77758b9bacc372fee590f734f256c3b1a8d55c137b3042ea7ef07e8e0953759c895cedf550b0b49eaaa837a80654!@mailstronghold-2.zmailcloud.com> <2B06780B8EE0354C70ECA60D@[192.168.1.30]> <20170215201531.GC3387@bender.cpp.edu> <WM!05e3245ecda5a40b6520e18c632ff0cbb60899aeee96d9a7ad736e6bc7f4637321949a16ffdfc0736a39bd7aec93ea0e!@mailstronghold-2.zmailcloud.com> <242E3F60A5A0A27989E6CFF7@[192.168.1.30]> <20170216023621.GD3387@bender.cpp.edu> <WM!e64825a13370ecd2c574348ad0bf9b821e2d7f6ba4aa1a03a74dd380d3fb666877db370e8004a85aaa48bc5aec9efdeb!@mailstronghold-2.zmailcloud.com> <C13A6C3818E82CDAC97C15C8@[192.168.1.30]> <20170217224457.GE3387@bender.cpp.edu> <7D65D44C-0350-4256-8994-F27DD1B8E623@uvm.edu> <WM!f18995f3d34d3256e8003b7f316361f6a89f381083c9c3b8e00597a505d0c5760e55c71442f3adc6c254b0d38b18425c!@mailstronghold-1.zmailcloud.com> <507D33782D21B69B197902F8@[192.168.1.30]>
- Thread-index: AQHShyp1IMPKvHUy00SlehSZS+bXM6FqTS8pgACI0gD//6577IAAu+wAgAERXquAAdKkAIAFU1YAgAAySMGAABEIgA==
- Thread-topic: 2.4.44 + ITS 8432 patch segfault in modify_add_values
On 2/21/17, 11:04, "Quanah Gibson-Mount" <quanah@symas.com> wrote:
--On Tuesday, February 21, 2017 1:04 PM +0000 Frank Swasey
<Frank.Swasey@uvm.edu> wrote:
> Years ago, I had code that did that and then I got a version of Net::LDAP
> that sent null attributes across the wire. Even back then OpenLDAP was
> upset by such behavior. I quickly updated my code to check if (in your
> case) @eduPersonAffiliation had zero entries and issue a proper
> $entry->delete('eduPersonAffiliation') call in that case. I've not had
> any issues since. Perhaps, your Net::LDAP module version has changed and
> it is sending what is being logged across the wire instead of the delete
> you are expecting.
Interesting... It would still be good for OpenLDAP to not crash in that
case, however. ;)
I obviously was not paying enough attention. I didn't realize OpenLDAP was crashing. I agree, that shouldn't happen - it should fail the update (IMHO) because null values for attributes are not legal.
- Frank