I can now confirm that the problem I was having is solved. I don't
use all the functionality of dnssec-trigger, though.
I would have appreciated your waiting at least another 48 hours before
assuming I had no further complaints.
zw
Your message dated Mon, 14 Nov 2016 04:05:27 +0100
with message-id
<1479092727.3578622.786639337.420db...@webmail.messagingengine.com>
and subject line Re: Bug#843532: [Pkg-dns-devel] Bug#843532: Bug#843532:
dnssec-trigger: broken by OpenSSL 1.1.0
has caused the Debian Bug report #
I have forwarded both patches to the nlnetlabs-maintainers list. Thanks.
--
Ondřej Surý
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mou
On 2016-11-10 12:10:41 [+0100], Ondřej Surý wrote:
> Sebastian,
Hi Ondřej,
> thanks for the patch. The 0.13~svn685-7 version in unstable includes
> your patch,
> and I would really appreciate if someone could test whether
> dnssec-trigger now
> works.
I managed to get around to test it. So the i
Sebastian,
thanks for the patch. The 0.13~svn685-7 version in unstable includes
your patch,
and I would really appreciate if someone could test whether
dnssec-trigger now
works.
Ondrej
--
Ondřej Surý
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.
control: tags -1 patch
On 2016-11-07 08:39:17 [-0500], Zack Weinberg wrote:
> Nov 07 08:34:17 moxana dnssec-triggerd[20281]: Nov 07 08:34:17
> dnssec-triggerd[20281] error: could not set SSL_OP_NO_SSLv2 crypto
> error:
could someone please check if the patch attached works? I am confide
Package: dnssec-trigger
Version: 0.13~svn685-6
Severity: critical
Justification: renders package unusable
On upgrading dnssec-trigger within unstable, the postinst fails with
errors from systemd:
Setting up dnssec-trigger (0.13~svn685-6) ...
Job for dnssec-triggerd.service failed because the cont
7 matches
Mail list logo
