Dear Kea Team, I am developing a custom hook library that handles lease commit, release, and expire events, and is loaded during Kea startup.
To study its integration and improve robustness, I intentionally introduced a segmentation fault in the hook logic. I observed that when the hook crashes, the main Kea process also crashes with it. This raises concerns regarding the resilience of the overall system when using third-party or experimental hooks. To help make Kea more resilient in such scenarios, I would like to understand: 1. How are hook libraries (.so) executed — are they run in a separate thread, separate process, or inline within the main DHCP process? 2. Is there currently any isolation or protection mechanism for Kea against hook-related crashes? 3. Are there best practices or plans for sandboxing hooks to prevent system-wide failure? My intent is not only to build safe extensions but also to explore ways to contribute toward improving Kea’s stability when handling faulty or experimental hook code. Thank you for your support and for building such a flexible DHCP platform. Best regards, Dipesh
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
