I noticed that there is a unbound_unixsock.diff in the contrib/ directory,
which makes the unbound and unbound-control to use unix sockets instead
of SSL connection.
I would like to ask if there is any particular reason why it is only
in the contrib/ dir and not part of the unbound source? Would it be
OK to integrate it into the source and just add a configure script
option like --with-unixsock-control (or something shorter )?
I can help with the integration in configure script.
I noticed that there is a unbound_unixsock.diff in the contrib/
directory, which makes the unbound and unbound-control to use unix
sockets instead of SSL connection.
I would like to ask if there is any particular reason why it is
only in the contrib/ dir and not part of the unbound source? Would
it be OK to integrate it into the source and just add a configure
script option like --with-unixsock-control (or something shorter
)?
I can help with the integration in configure script.
It is already a feature of the unbound source! Use /tmp/unbound.sock
for control-interface: in unbound.conf. You can also disable the
certificate checks with an option.
> Hi all.
>
> I noticed that there is a unbound_unixsock.diff in the contrib/
> directory, which makes the unbound and unbound-control to use unix
> sockets instead of SSL connection.
>
> I would like to ask if there is any particular reason why it is
> only in the contrib/ dir and not part of the unbound source? Would
> it be OK to integrate it into the source and just add a configure
> script option like --with-unixsock-control (or something shorter
> )?
>
> I can help with the integration in configure script.
It is already a feature of the unbound source! Use /tmp/unbound.sock
for control-interface: in unbound.conf. You can also disable the
certificate checks with an option.
Oh, I didn't notice it. Thanks for pointing it out. I will test it. Thank you!
)?