As noted in http://d.root-servers.org/renumber.html, the change will be
done on the 3rd Jan and the old IP address will be retried 6 months
later.
Could we get proposed-update packages before the 3rd Jun (when the old
IP will stop responding)?
I'm presuming that the Ubuntu guys are waiting until
Hi guys,
I am very happy to confirm that this worked great.
First it was gave me an indication that the remote server was not
responding (as per
http://bitcube.co.uk/content/puppet-errors-explained) and then it
correclt diagnosed a mismatched server identity.
Thanks for getting this fix in.
Public bug reported:
Binary package hint: bind9
As noted here:
http://wiki.debian.org/DNSSEC#BIND9
The are some configuration changes required to enable DNSSEC validation.
I think it would be nicer if things could be made easier.
Create an empty file /etc/bind/named.conf.keys
Include the
All versions of BIND that Ubuntu has ever published could do with improvements
in making DNSSEC easier.
However, as noted in the linked instructions, the specific suggestions
apply to Bind 9.7+
Which, according to http://packages.ubuntu.com/search?keywords=bind9 is
Ubuntu 10.04 (Lucid) and
** Changed in: bind9 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/782614
Title:
make configuring DNSSEC validation easier
--
libdbi is now clear in the later version of Ubuntu.
Any progress on an updated rrdtool?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rrdtool in Ubuntu.
https://bugs.launchpad.net/bugs/605871
Title:
[needs-packaging] rrdtool
** Patch added: 0001-Add-a-named.conf.keys-file-for-storing-various-keys.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256290/+files/0001-Add-a-named.conf.keys-file-for-storing-various-keys.patch
--
You received this bug notification because you are a member
** Patch added: 0002-Install-the-named.conf.keys-file.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256307/+files/0002-Install-the-named.conf.keys-file.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Patch added: 0003-Include-the-named.conf.keys-file.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2256349/+files/0003-Include-the-named.conf.keys-file.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Patch added: 0004-dnssec-in-options.patch
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/782614/+attachment/2257805/+files/0004-dnssec-in-options.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
DNSSEC will place an additional burden on the network and, in particular, the
infrastructure based DNS servers.
The rationale to have the root key defined here but not used is that
will use some of the existing DNS infrastructure (via use of RFC5011)
and allow server operators to gauge load.
I
Note, I just checked Fedora 15 and the root key is setup similarly and is
*enabled* by default as well.
So you might just want to do so within Ubuntu as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
Public bug reported:
Hi,
openssh can lookup a host's key in the DNS (via the SSHFP record) and
use it compare hosts presented public key.
VerifyHostKeyDNS yes
I believe that is the connection is secured via DNSSEC that this option
will allow for the host's key to be automagically accepted.
Meant to say that /etc/ssh/config would be the place to put the default
configuration.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/825825
Title:
have DNS based verification
Public bug reported:
Binary package hint: puppet
Hi,
There are many versions of puppet, fortunately lucid (10.04) has a
relatively new version (merely called legacy from puppetlabs).
Unfortunately it has a number of bugs / issues, one of which I have
recently encountered is an underlying bug
See if you can contact someone from the Canonical server team. Personally I'd
also try to contact the ntp maintainer via IRC too.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ntp in ubuntu.
https://bugs.launchpad.net/bugs/104525
Public bug reported:
Binary package hint: bind9
1.
root@ns3:~# lsb_release -rd
Description:Ubuntu 10.04.2 LTS
Release:10.04
2.
ot@ns3:~# apt-cache policy bind9
bind9:
Installed: 1:9.7.0.dfsg.P1-1ubuntu0.1
Candidate: 1:9.7.0.dfsg.P1-1ubuntu0.1
Version table:
***
Hi Sebastien,
How we can help diagnose the problem? The issue description is wrong
(since earlier commentators indicated that it also failed on amd64).
I have an i386 and amd64 machine and am only expericing this issue on
the amd64 one.
Thanks,
Anand
--
ssh Agent admitted failure to sign
Public bug reported:
Binary package hint: samba
Hi,
Whilst perusing my ~/.xsession-error file, I noticed nautilius-share
complaining.
It turns out it is trying to do 'net usershare info', which was failing.
Please set in smb.conf:
usershare path = /var/lib/samba/usershares
This is okay,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25008692/Dependencies.txt
--
please set usershare path
https://bugs.launchpad.net/bugs/357569
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
I'd rather file a separate bug for each of those issues you mention
- since this change should be uncontroversial, I can not see any
reason to not do it.
Whereas differing people might agree / disagree about whether to
enable / disable usershares by default.
Thanks,
Anand
On Fri, Apr 10, 2009
The uncontrovorsial changes are the ones I already elaborated.
Please let me know if you did not understand my English and I will try
to explain things once again.
Obviously the bug report asking for the directory to be created on the
filesystem has not been filed.
I will file it shortly,
Public bug reported:
Binary package hint: sysstat
1)
eve[~]% lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
2)
eve[~]% apt-cache policy sysstat
sysstat:
Installed: 9.0.3-2ubuntu1
Candidate: 9.0.3-2ubuntu1
Version table:
*** 9.0.3-2ubuntu1 0
500
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35304279/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/35304289/XsessionErrors.txt
--
cron job is overly noisy
https://bugs.launchpad.net/bugs/477333
You received this bug
Public bug reported:
1)
eve:[~]% lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
2)
eve:[~]% apt-cache policy libvirt-bin
libvirt-bin:
Installed: 0.7.5-5ubuntu3
Candidate: 0.7.5-5ubuntu3
Version table:
*** 0.7.5-5ubuntu3 0
500
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/38399177/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38399178/Dependencies.txt
** Attachment added: Df.txt
http://launchpadlibrarian.net/38399179/Df.txt
** Attachment added:
Hi,
Yes, it occurs all the time.
Now occuring with 0.7.5-5ubuntu7, let me know if you would like to do
any further investigation.
Thanks,
Anand
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
--
package libvirt-bin 0.7.5-5ubuntu3 failed to install/upgrade: subprocess
OK - it appears that /etc/passwd.lock and /etc/shadow.lock existed, for some
reason, and was the cause of the problem. I removed those file and was able to
complete installed.
Closing.
** Changed in: libvirt (Ubuntu)
Status: New = Fix Released
--
package libvirt-bin 0.7.5-5ubuntu3
Public bug reported:
dig, as supplied, will not validate a DNSSEC domain.
The +sigchase option should cause validation to occur but it does not.
As noted in http://bryars.eu/2010/08/validating-and-exploring-dnssec-
with-dig/ if a file called 'trusted-key.key' is present then dig will
use that.
Considering that the 'bind9' package ships the root key (in
/etc/bind/bind.keys), I see no reason why it should not also be shipped
in the dnsutils package as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
30 matches
Mail list logo
