> Is it serious? The file managed-keys.bind looks normal.
It's concerning. How many 5011-maintained zones are you running? Can I
see your managed-keys.bind file?
I would expect the result of this to be that keys are not properly updated
in managed-keys.bind until the problem with committing to
On Thu, Oct 29, 2009 at 09:24:48AM +0100,
Stephane Bortzmeyer wrote
a message of 25 lines which said:
> > - Support for RFC 5011 automated trust anchor maintenance (see
> > README.rfc5011 for additional details).
Hmmm, it suddenly had a problem:
02-Nov-2009 10:59:14.945 zone manage
On Tue, Oct 20, 2009 at 08:29:20PM +,
Evan Hunt wrote
a message of 836 lines which said:
> - Support for RFC 5011 automated trust anchor maintenance (see
> README.rfc5011 for additional details).
Seems to work fine, thanks.
With:
managed-keys {
"se." initial-key
> Will you be adding RSASHA256 support in the 9.5.x and 9.6.x series? It
> might be a bit optimistic to expect everyone to move to 9.7.x by 2010-07-01,
> if that's when the root zone is going to be *really* signed (with RSASHA256,
> according to current reports).
Not 9.5.x, as it lacks NSEC3 supp
On Oct 28 2009, Evan Hunt wrote:
You aren't going to wait for the RFC? - it doesn't seem to be out yet.
Or maybe you are predicting that it will be out before 9.7.0b2 is...
It's out now (RFC 5702), so this is a moot point--but we were mainly
waiting for IANA to pick the final codepoints, not s
> You aren't going to wait for the RFC? - it doesn't seem to be out yet.
> Or maybe you are predicting that it will be out before 9.7.0b2 is...
It's out now (RFC 5702), so this is a moot point--but we were mainly
waiting for IANA to pick the final codepoints, not so much for the
RFC to be finalize
On Wed, Oct 28, 2009 at 03:17:54PM +,
Chris Thompson wrote
a message of 13 lines which said:
> You aren't going to wait for the RFC?
It is in AUTH48 (the last step before publication, theoretically
meaning that the people involved have 48 h to make remarks).
After all, ldns already has
On Oct 28 2009, Evan Hunt wrote:
Apparently, support for the new algorithms RSASHA256 and RSASHA512 is
not included? Is it planned for 9.7 or shall I wait 9.8?
That will be in 9.7.0b2.
You aren't going to wait for the RFC? - it doesn't seem to be out yet.
Or maybe you are predicting that it
> Apparently, support for the new algorithms RSASHA256 and RSASHA512 is
> not included? Is it planned for 9.7 or shall I wait 9.8?
That will be in 9.7.0b2.
--
Evan Hunt -- e...@isc.org
Internet Systems Consortium, Inc.
___
bind-users mailing list
bind-
On Tue, Oct 20, 2009 at 08:29:20PM +,
Evan Hunt wrote
a message of 836 lines which said:
>BIND 9.7.0b1 is now available.
Apparently, support for the new algorithms RSASHA256 and RSASHA512 is
not included? Is it planned for 9.7 or shall I wait 9.8?
% bind/bin/dnssec/dn
At Mon, 26 Oct 2009 11:42:53 -0400,
"Gerry Scott" wrote:
> OpenSolaris build 125 includes execinfo.h within the /usr/include directory.
> Also, backtrace() functionality has been included within the OS since build
> 63.
>
> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6536146
Okay
MEI Tatuya / [mailto:jin...@isc.org]
Sent: Monday, October 26, 2009 4:33 AM
To: gscot...@gmail.com
Cc: bind-us...@isc.org
Subject: Re: call for testers (Re: ISC BIND 9.7.0b1 is now available)
At Thu, 22 Oct 2009 10:09:12 -0400,
"Gerry Scott" wrote:
> Backtrace executes successfully
> Date: Wed, 21 Oct 2009 15:50:00 -0700
> From: JINMEI Tatuya / ...@l@C#:H(B
>
>
> 1. build 9.7.0b1
> 2. go to the "bind-9.7.0b1/bin/tests" directory
> 3. % make backtrace_test
> 4. % ./backtrace_test
metis% uname -a
SunOS metis 5.9 Generic_122300-31 sun4u sparc SUNW,Ultra-1
metis% make back
At Thu, 22 Oct 2009 10:09:12 -0400,
"Gerry Scott" wrote:
> Backtrace executes successfully on the latest build of OpenSolaris for SPARC
> (snv_125) with gcc version 3.4.6
>
> # uname -a
> SunOS nemesis 5.11 snv_125 sun4u sparc SUNW, 5-slot Sun Enterprise E3500
>
> # gcc -v
> Reading specs from
/
Sent: Wednesday, October 21, 2009 8:18 PM
To: bind-us...@isc.org
Subject: Re: call for testers (Re: ISC BIND 9.7.0b1 is now available)
At Wed, 21 Oct 2009 15:50:00 -0700,
JINMEI Tatuya wrote:
> On success, "backtrace_test" simply exits without any output (I know
> it's not a g
> > Possibly also useful to report success here so that many people aren't
> > needlessly repeating the same test.
- NetBSD 4.99.62 amd64, gcc 4.1.3 20080202 prerelease (NetBSD nb1 20080202)
- NetBSD 5.0.0_PATCH i386, pcc 0.9.9 (HEAD) for i386-unknown-netbsdelf5.0.0.
___
JINMEI,
we're not using sparc for our bind installations, but this is a feedback
on your 'call for testers' (bind compilation went successfully on both
compilers):
solaris 10 sparc, sun studio 12u1 compiler:
$ uname -a
SunOS chuck 5.10 Generic_141414-10 sun4u sparc SUNW,Sun-Fire-V440
$ cc -V
cc
~/bind-9.7.0b1/bin/tests# uname -rna
FreeBSD hostname 7.2-STABLE FreeBSD 7.2-STABLE #0: Tue Aug 11 20:18:22 UTC
2009 r...@hostname:/usr/obj/usr/src/sys/GENERIC amd64
[10:09] ttyp0/0 {861}~/bind-9.7.0b1/bin/tests# gcc --version
gcc (GCC) 4.2.1 20070719 [FreeBSD]
Copyright (C) 2007 Fr
At Wed, 21 Oct 2009 20:19:59 -0400,
Dave Knight wrote:
>
> > If the test fails
> > on your platform, please report it to bind9-b...@isc.org, including
> > the OS, its version, and hardware architecture (x86, amd64, sparc,
> > etc).
> Possibly also useful to report success here so that many peopl
On 2009-10-21, at 8:19 PM, Dave Knight wrote:
x86_64 / Mac OS X 10.6.1 / Darwin dhcp4.sanxion.org 10.0.0 Darwin
Kernel Version 10.0.0: Fri Jul 31 22:47:34 PDT 2009;
root:xnu-1456.1.25~1/RELEASE_I386 i386
i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5646)
x86 / Ubuntu 9.04
On 2009-10-21, at 6:50 PM, JINMEI Tatuya / 神明達哉 wrote:
Dear beta testers,
At Tue, 20 Oct 2009 20:29:20 +,
Evan Hunt wrote:
BIND 9.7.0b1 is now available.
[snip]
- On some platforms, named and other binaries can now print out
a stack backtrace a
At Wed, 21 Oct 2009 15:50:00 -0700,
JINMEI Tatuya wrote:
> On success, "backtrace_test" simply exits without any output (I know
> it's not a good UI); if something goes wrong it will dump some warning
> messages to stderr and exit with a non-0 exit code. If the test fails
> on your platform, ple
Dear beta testers,
At Tue, 20 Oct 2009 20:29:20 +,
Evan Hunt wrote:
>BIND 9.7.0b1 is now available.
[snip]
> - On some platforms, named and other binaries can now print out
> a stack backtrace an assertion failure, to aid in debugging.
I'd like to know pl
BIND 9.7.0b1 is now available.
BIND 9.7.0b1 is the first beta release of BIND 9.7.0.
Overview:
BIND 9.7 includes a number of changes from BIND 9.6 and earlier
releases. Most are intended to simplify DNSSEC configuration
and operation.
New fe
24 matches
Mail list logo
