[Kea-users] Need help defining custom options

[James Sumners]

On January 31, 2017 at 2:20:50 PM, Tomek Mrugalski (tomasz at isc.org<mailto:tomasz at isc.org>) wrote:

Adding another release is something we can do, but only if major issue
is discovered that cannot wait till the next planned release. That
typically means a security issue or a very serious bug that prevents
many deployments from operating normally. Sadly, this bug here is not
such a case.

Having said that, I may try to help you with this. Would you be willing
to run git version of the code? I can review the fix and it could be
ready in couple days. If not, would a patch backported to 1.1.0 be ok?

As I mentioned previously, I really don’t want to maintain my own build. Currently, I’m using the package available in Void Linux. When I deploy to production, if I am able to, I will be using the one available in EPEL for RHEL 7. Both of them are going to be packaging the current stable and any fixes that come along for that. Hopefully that means EPEL will package 1.2.

As a work around for this issue I have created a filter for my Ansible playbook that will convert the plain ASCII string to a hex encoded string. I don’t get to write the values directly in the configuration template, but it’s good enough. I just need to figure out if it is actually working. I’m telecommuting today so I can’t do a hands on test. But I plan to look at it first thing tomorrow.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20170131/70a29177/attachment.htm>