On Mon, 2018-10-01 at 20:23 +0200, Lee Garrett wrote:
> Hi,
> 
> Any update on this bug? dnssec-trigger will be autoremoved due to
> this bug
> tomorrow. I'd like to see it in buster, though.



Ooops I forgot, Also does this bug impact unbound? I tried checking the
unbound maintainer scripts and they're not doing anything to handle
this case

What's 
sudo -s openssl x509 \
  -in /etc/dnssec-trigger/dnssec_trigger_control.pem  -text | \
  grep 'Public-Key'

Look like on an effected system?

On mine is 3072, and I don't seem to be impacted.

I'm guessing I can use that to determine if I need to regenerate the
key

The other option is to just delete the key and regenerate it on the
specific version upgrade.

What do others think
Diane

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to