On Mon, Oct 01, 2018 at 08:06:25PM -0700, Diane Trout wrote:
> 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 do
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 t
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.
Regards,
Lee
Thank you for the detailed bug report.
I'll need to think a bit about the maintainer script...
On Fri, 2018-05-18 at 01:27 +, brian m. carlson wrote:
> Package: dnssec-trigger
> Version: 0.15+repack-1
> Severity: important
>
> I have two existing installations of dnssec-trigger that have 1
Package: dnssec-trigger
Version: 0.15+repack-1
Severity: important
I have two existing installations of dnssec-trigger that have 1536-bit
client and server keys. I'm using the OpenSSL from experimental, which
rejects keys of less than 2048 bits in size, as they are presently
considered too weak.
5 matches
Mail list logo