> From: =?UTF-8?Q?Marek_Vavru=C5=A1a?=
> There's a functionality [1] to do all these things (and more), you
> just can't read/write complicated rules from RPC compatible format
> (DNS zone files). Feel free to contribute of course.
On the contrary, as far as I can see
Hi Vernon,
There's a functionality [1] to do all these things (and more), you
just can't read/write complicated rules from RPC compatible format
(DNS zone files). Feel free to contribute of course.
Marek
[1]:
http://knot-resolver.readthedocs.io/en/stable/modules.html#dns-application-firewall
> From: =?UTF-8?B?VmxhZGltw61yIMSMdW7DoXQ=?=
> The current very limited implementation of RPZ in knot-resolver [1] is
> done via a couple dozen lines of lua code, i.e. only JIT-compiled. The
> approach might remain similar, perhaps a bit more modularized, but in
>
> From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?=
> draft-ietf-dnsop-dns-rpz expired on 2017-09-10, i.e. did not receive any
> update from 2017-03-09.
>
> Is there a real apetite for work on this document?
The change described in Suzanne Woolf's mail that you quoted is
awaiting a
Hi Petr
On Fri, Oct 06, 2017 at 03:56:20PM +0200, Petr Špaček wrote:
> Hello dnsop,
>
> draft-ietf-dnsop-dns-rpz expired on 2017-09-10, i.e. did not receive any
> update from 2017-03-09.
>
> Is there a real apetite for work on this document?
No answer for this question, but see below...
> We
Hello dnsop,
draft-ietf-dnsop-dns-rpz expired on 2017-09-10, i.e. did not receive any
update from 2017-03-09.
Is there a real apetite for work on this document?
We are considering RPZ implementation for Knot Resolver next year but if
the document is not going to move forward I would rather