Package: dnssec-trigger
Version: 0.17+repack-1
Severity: serious
Setting up dnssec-trigger (0.17+repack-1) ...
Job for dnssec-triggerd.service failed because the control process exited with
error code.
See "systemctl status dnssec-triggerd.service" and "journalctl -xe" for details.
invoke-rc.d: i
Hi,
Axel Beckert wrote:
> The syslog shows again this:
>
> Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59
> dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file crypto
> error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small
Attached the output o
On Mon, 2019-01-14 at 14:35 +0100, Axel Beckert wrote:
> Hi,
>
> Axel Beckert wrote:
> > The syslog shows again this:
> >
> > Jan 14 07:18:59 c-cactus2 dnssec-triggerd[22039]: Jan 14 07:18:59
> > dnssec-triggerd[22039] error: Error in SSL_CTX use_certificate_file
> > crypto error:140AB18F:SSL rou
Hi,
in the course of looking into the upgrade failure, I ended up purging
dnssec-trigger and then installed it again. I notice this creates keys
and config files in both /etc/ and /etc/dnssec-trigger?! Different to
Alex, I get traceback in the middle of the log (also for subsequent
attempts to 'ap
Hi Diane,
Diane Trout wrote:
> Was dnssec-triggerd running before the upgrade?
I think so.
> Was there then an
> upgrade to openssl 1.1.1? and then finally it wouldn't start?
That one was much earlier IIRC, like weeks ago.
Anyway, I've now got a second machine with the same symptoms, just now
On Mon, 2019-01-14 at 21:25 +0100, Florian Schlichting wrote:
> Hi,
>
> in the course of looking into the upgrade failure, I ended up purging
> dnssec-trigger and then installed it again. I notice this creates
> keys
> and config files in both /etc/ and /etc/dnssec-trigger?! Different to
> Alex, I
On Mon, Jan 14, 2019 at 01:31:28PM -0800, Diane Trout wrote:
> I'm a little worried about just rm-ing previously invalid locations for
> configuration files. Might you have suggestions about how to safely
> clean up dnssec-triggers configuration file mess? (At the very least it
> seems like it shou
On Tue, 2019-01-15 at 00:08 +0100, Florian Schlichting wrote:
>
> Before thinking about cleanup, I'd start by making sure that fresh
> installs don't re-create problems. At the moment, purging dnssec-
> trigger
> leaves two keypairs in /etc; and when I rm them manually, and again
> install dnssec-
Ok
I found the place that was causing the segfault on installation, made a
patch, it worked for me, and I pushed a new release.
(Fixes also sent upstream)
dnssec-trigger should also now only look for configuration files in
/etc/dnssec-trigger, and it shouldn't try to create ones in /etc any
more
Control: reopen -1
Control: found -1 0.17+repack-2
Hi Diane,
Diane Trout wrote:
> I found the place that was causing the segfault on installation, made a
> patch, it worked for me, and I pushed a new release.
Thanks for caring and looking into it.
> Please let me know if dnssec-trigger-0.17+rep
version: 0.17+repack-3
tag: pending
I have a new version (hopefully uploaded successfully) where I fixed
dnssec-trigger-control-setup to not generate new keys or certificates
if called repeatedly. So now the code to delete small keys should get
called.
I also included upstream's fix for the segfa
On Wed, 2019-01-16 at 08:55 +0100, Axel Beckert wrote:
>
>
> # summary of how this script can be called:
> #* `configure'
> [...]
> case "$1" in
> configure)
> # configure the control channel if run for the first time
> if [ -z "$2" ]; then
> dnssec-trigg
12 matches
Mail list logo
