[Bug 1126488] Re: libvirt instance of dnsmasq in raring fails to forward DNS requests

2013-02-21 Thread cp
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-0198

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1126488

Title:
  libvirt instance of dnsmasq in raring fails to forward DNS requests

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1126488/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1090593] Re: D.ROOT-SERVERS.NET changing January 3rd 2013

2013-01-08 Thread cp
Although not a serious problem, admins running LTS releases could be waiting a 
long time for the packages to include the correct IPv4 D root server.

I asked LaMont Jones, one of the Debian bind9 maintainers, about this D root 
change issue and he said: 
It's fixed in 1:9.8.4.dfsg.P1-2, and will be in 9.9.2 when it makes it into 
sid.  

I have brought up the issue with the Ubuntu Server Team, see
https://lists.ubuntu.com/archives/ubuntu-
server/2013-January/thread.html#6469.

I have manually updated the bind9 servers I run, in case someone wants to know 
how...
# wget http://www.internic.net/domain/named.root
# cat named.root  /etc/bind/db.root 
# service bind9 restart

-- 
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/1090593

Title:
   D.ROOT-SERVERS.NET changing January 3rd 2013

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1090593] [NEW] D.ROOT-SERVERS.NET changing January 3rd 2013

2012-12-14 Thread cp
Public bug reported:

Currently we have:
/etc/bind/db.root:D.ROOT-SERVERS.NET.  360  A 128.8.10.90

The new IPv4 address for this authority is 199.7.91.13

The current IPv6 address for this authority is 2001:500:2d::d and it
will continue to remain unchanged.

See http://d.root-servers.org/

** Affects: bind9 (Ubuntu)
 Importance: Undecided
 Status: 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/1090593

Title:
   D.ROOT-SERVERS.NET changing January 3rd 2013

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1090593/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 728879] [NEW] check_perms -f broke mailman

2011-03-03 Thread cp
Public bug reported:

Binary package hint: mailman

mailman (1:2.1.13-1ubuntu0.2)

check_perms -f changed the permissions on /var/lib/mailman/data/virtual-
mailman and exim4 couldn't read it.  This caused exim4 to create a panic
log, not good!

# cat /var/log/exim4/paniclog 
2011-03-03 21:06:25 failed to expand condition 
${lookup{$local_part@$domain}lsearch{/var/lib/mailman/data/virtual-mailman}{1}{0}}
 for mailman_router router: failed to open 
/var/lib/mailman/data/virtual-mailman for linear search: Permission denied 
(euid=104 egid=112)
2011-03-03 21:17:58 failed to expand condition 
${lookup{$local_part@$domain}lsearch{/var/lib/mailman/data/virtual-mailman}{1}{0}}
 for mailman_router router: failed to open 
/var/lib/mailman/data/virtual-mailman for linear search: Permission denied 
(euid=104 egid=112)

# ls -l /var/lib/mailman/data/virtual-mailman
-rw-rw 1 root list 9633 2011-02-28 23:51 
/var/lib/mailman/data/virtual-mailman

Simple fix not using check_perms.
# chgrp Debian-exim /var/lib/mailman/data/virtual-mailman

If the lists were busy or I hadn't noticed the paniclog until later,
this would have resulted in lost mail!

Running check_perms still shows many permission problems, over 200, but
they haven't affected the lists or the archives.  It appears the way
mailman is packaged with the many symbolic links contributed to this
problem.

This bug was found in mailman on Ubuntu 10.04. but I suspect it is an
issue for many of the packaged versions of mailman in Ubuntu and Debian.

** Affects: mailman (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mailman in ubuntu.
https://bugs.launchpad.net/bugs/728879

Title:
  check_perms -f broke mailman

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs