[Bug 1384503] Re: rsync fails on large files with compression
I attempted to SRU a patch almost a year ago. And that was after two other people confirmed the patch worked for them. In reply to my email Alberto Salvia Novella said on Mon, Jan 12, 2015 at 5:14 PM C Peters: > https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367 > Can someone nominate this for a SRU? Done ;) Please see Comment #6 of bug report https://bugs.launchpad.net/rsync/+bug/1300367. The fixed package has been available in my Launchpad PPA since 2014-10-20. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1384503 Title: rsync fails on large files with compression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+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 1406729] Re: dig does not have a default trusted key
I vote no, if someone is setting up or testing DNSSEC, let's not encourage them to use a broken dig option! I tried using the following command and dig core dumped. Note: www is setup as a CNAME. dig +trusted-key=trusted-key.key +topdown +sigchase +multiline -ta www.tuxedo.net I was wondering if I had done something wrong with DNSSEC... But other tools show (I think) it looks ok. drill -TD -k ../trusted-key.key www.tuxedo.net # See footnote 1 http://dnsviz.net/d/www.tuxedo.net/dnssec/ And some more digging and I found: The option is not compiled in by default upstream because it is broken. See: https://lists.isc.org/pipermail/bind-users/2012-May/087779.html https://lists.isc.org/pipermail/bind-users/2012-May/087781.html dig +trusted-key=trusted-key.key +topdown +sigchase +multiline -ta com ... ;; OK a DS valids a DNSKEY in the RRset ;; Now verify that this DNSKEY validates the DNSKEY RRset ;; VERIFYING DNSKEY RRset for com. with DNSKEY:30909: success ;; We are in a Grand Father Problem: See 2.2.1 in RFC 3568 ;; ERROR : com. is not a subdomain of: com. FAILED name.c:2151: REQUIRE(source-length 0) failed, back trace #0 0x7f1a1cda5954 in ?? #1 0x7f1a1cda58ba in ?? #2 0x7f1a1d4a7bdc in ?? #3 0x7f1a1dc45f72 in ?? #4 0x7f1a1dc48397 in ?? #5 0x7f1a1dc4a3d2 in ?? #6 0x7f1a1cdc7af6 in ?? #7 0x7f1a1cb80182 in ?? #8 0x7f1a1c8acefd in ?? Aborted (core dumped) I also compiled bind-9.9.6-P1 to test if it was fixed in a newer release, and it is still broken. Footnote 1: Note drill is currently part of ldnsutils package and not unbound. https://www.nlnetlabs.nl/projects/drill/ -- 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/1406729 Title: dig does not have a default trusted key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1406729/+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 1300367] Re: rsync 3.1.0 and 3.0.9 incompatibility
Attached is a patch which seems to fix the bug for Ubuntu Trusty or 14.04. Please test the package from my PPA and confirm it works OK. https://launchpad.net/~cp/+archive/ubuntu/bug-fixes/+packages The easy way to install it: sudo add-apt-repository ppa:cp/bug-fixes sudo apt-get update sudo apt-get upgrade Changelog rsync (3.1.0-2ubuntu0.2) trusty; urgency=medium * Use included zlib as transfers failed when using -z with the separate zlib. (LP: #11300367) - debian/rules: Add -Izlib to CPPFLAGS and change .configure to use -with-included-zlib=yes - debian/control: Remove Build-Depends zlib1g-dev My testing shows transfers with the -z option are working, but the real test will be when my backups run late tonight. ;) ** Patch added: Use rsync's internal zlib https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1300367/+attachment/4240742/+files/rsync-trusty-zlib-internal.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1300367 Title: rsync 3.1.0 and 3.0.9 incompatibility To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1300367/+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 1300133] Re: Generate ED25519 host keys on upgrade
# ssh-keygen -A ssh-keygen: generating new host keys: RSA1 ED25519 I don't think we want to add the old RSA1 keys, just the new ED25519. -- 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/1300133 Title: Generate ED25519 host keys on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1300133/+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 1300133] [NEW] Generate ED25519 host keys on upgrade
Public bug reported: openssh (1:6.5p1-1) unstable; urgency=medium ... * Generate ED25519 host keys on fresh installations. Upgraders who wish to add such host keys should manually add 'HostKey /etc/ssh/ssh_host_ed25519_key' to /etc/ssh/sshd_config and run 'ssh-keygen -q -f /etc/ssh/ssh_host_ed25519_key -N -t ed25519'. ... -- Colin Watson cjwat...@debian.org Mon, 10 Feb 2014 14:58:26 + Most users and many administrators are not going to notice the new host key capabilities when it is buried in a changelog. We should at least give them a obvious hint about it. Even better would be to prompt the user to generate the keys with a debconf question like was recently done with the Change to PermitRootLogin without-password. I would like to label this as a security vulnerability, but that may be a bit over the top, it would be a security improvement! ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- 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/1300133 Title: Generate ED25519 host keys on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1300133/+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 1247148] Re: rndc addzone isn't working. fix available
snippet of /etc/apparmor.d/usr.sbin.named # /etc/bind should be read-only for bind # /var/lib/bind is for dynamically updated zone (and journal) files. # /var/cache/bind is for slave/stub data, since we're not the origin of it. # See /usr/share/doc/bind9/README.Debian.gz /etc/bind/** r, /var/lib/bind/** rw, /var/lib/bind/ rw, /var/cache/bind/** lrw, /var/cache/bind/ rw, Pavel's proposed solution could cause other issues with apparmor. Furthermore Pavel should place the zone files in /var/lib/bind/. $ ls -ld /var/lib/bind/master/ drwxrws--- 3 root bind 4096 Jun 30 23:08 /var/lib/bind/master/ A directory from a hidden master containing one of my DNSSEC enabled zones, a zone which is configured to automatically rotate the ZSK or zone signing key: $ sudo ls -la /var/lib/bind/master/tuxedo.net total 104 drwxrws--- 2 bind bind 4096 Nov 8 18:03 . drwxrws--- 3 root bind 4096 Jun 30 23:08 .. -rw-r--r-- 1 root bind 1858 Sep 24 18:51 tuxedo.net.hosts -rw-r--r-- 1 bind bind 512 Sep 24 18:51 tuxedo.net.hosts.jbk -rw-r--r-- 1 bind bind 7509 Nov 8 18:03 tuxedo.net.hosts.signed -rw-r--r-- 1 bind bind 76419 Nov 8 17:48 tuxedo.net.hosts.signed.jnl -- 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/1247148 Title: rndc addzone isn't working. fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1247148/+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 1247148] Re: rndc addzone isn't working. fix available
Perhaps a better approach would be to modify /etc/default/bind9. $ cat /etc/default/bind9 # run resolvconf? RESOLVCONF=no # startup options for the server OPTIONS=-u bind -- 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/1247148 Title: rndc addzone isn't working. fix available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1247148/+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 1214749] [NEW] Sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main)
Public bug reported: Please sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/tests: Add autopkgtest. * Fix FTBFS: correct expected Python.h location in configure script (LP: #1098162). - d/control: add build dependency on dh-autoreconf - d/rules: use dh_autoreconf and dh_autoreconf_clean - d/patches/80_python_h_location.patch: patch configure.in * Fix FTBFS: correct expected Python.h location in configure script (LP: #1098162). - d/control: add build dependency on dh-autoreconf - d/rules: use dh_autoreconf and dh_autoreconf_clean - d/patches/80_python_h_location.patch: patch configure.in To check for possible merges I compared the Debian 2.1.15-1 and Ubuntu 2.1.15-1ubuntu2 source packages with diff -ru and then compared the changes to Debian's 2.1.16~rc2-1. I also checked with Yolanda Robla yolanda.ro...@canonical.com and Robie Basak robie.ba...@canonical.com about possible merges. It appears all of Ubuntu's changes have made it into the new Debian package or Mailman upstream. I tested the packages on raring using my production raring VPS and it appears to be running without any issues. The results of my saucy builds are posted at: https://launchpad.net/~cp/+archive/net/+sourcepub/3435869/+listing-archive-extra Changelog entries since current saucy version 1:2.1.15-1ubuntu2: mailman (1:2.1.16~rc2-1) unstable; urgency=low [ Thijs Kinkhorst ] * New upstream release candidate. - Exposes message-id to templates (closes: #614340). * Remove obsolete patches, applied upstream: 21_newlist_help.patch * Updates to Russian debconf templates, thanks Ivan Krylov! (closes: #710268). * Needs at least version 3.8.0 of logrotate (closes: #687215). * Add autopkgtests, thanks Yolanda Robla! (closes: #710095) * Packaging cleanup: checked for policy 3.9.4, update Vcs URL, recommend default-mta instead of exim4. [ Thorsten Glaser ] * Prevent losing stderr in the init script when there are many lists. (closes: #702002) * debian/watch: mangle the epoch away so DDPO is green again. -- Thijs Kinkhorst th...@debian.org Sun, 04 Aug 2013 12:00:05 +0200 ** 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/1214749 Title: Sync mailman 1:2.1.16~rc2-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailman/+bug/1214749/+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
