[Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
For those who can't wait, I've built a version with this fix in my PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
It seems like the ball has been dropped on this, possibly by me. Is there something I need to do to get someone to upload a new version using the debdiff I provided? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
This was fixed in 4.3-8 and so is already fixed in utopic and later. It will require an SRU to fix in trusty. I've attached a debdiff containing the needed change. ** Description changed: Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341 The Debian bug includes complete reproduction case. Basically: with .inputrc containing set revert-all-at-newline On Go back in the commandline history, edit a command, then submit a different command (may be empty) Such as: $ ls something $ Attached diff is confirmed to fix the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bash 4.3-7ubuntu1.5 [origin: goobuntu-trusty-testing-desktop] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Feb 17 15:49:30 2015 SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.bash.bashrc: [modified] mtime.conffile..etc.bash.bashrc: 2015-01-27T03:27:18.751405 + + + [Test Case] + + Adapted from the Debian bug report: + + 1. echo "set revert-all-at-newline on" > bug.inputrc + 2. INPUTRC=bug.inputrc bash + 3. echo hello + 4. ^P^U^N^M [Hold down control and type "punm".] + + Bash should die immediately with SIGABRT. + + + [Regression Potential] + + Relatively low. + + The change has no effect at all unless _rl_revert_all_lines() is called, + which only happens if revert-all-at-newline is set, and then only when a + newline is typed. So, the potential for regression is essentially zero for + non-interactive shells and for anyone not using revert-all-at-newline (which + is not the default). + + Further, this change appeared upstream and in both Debian and Ubuntu over + a year ago, so it's had plenty of public testing. + + lib/readline/misc.c:_rl_revert_all_lines() contains a loop which iterates + over history entries, reverting changes to each history entry. This patch + causes entry->data, which points to the per-entry undo list, to be cleared + before reverting edits rather than after. At first glance, this shouldn't + make any difference. However, it prevents rl_do_undo() from replacing the + history entry with one reflecting the change. Otherwise, the entry gets + freed, leaving _rl_revert_all_lines() with an invalid pointer. + + _Not_ having an invalid pointer and double-free certainly can't be worse + than the current situation. Since we're avoiding is making the pointer + invalid rather than not doing the free, the chance of a new leak is pretty + much nonexistent. ** Patch added: "debdiff containing the upstream patch" https://bugs.launchpad.net/gnubash/+bug/1422795/+attachment/4497315/+files/bash-readline-revert.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1422795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
This was reported to the bug-bash mailing list and has been fixed upstream, but there doesn't appear to be a bug tracker. ** Also affects: gnubash Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1422795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422795] Re: bash crashes often if inputrc contains revert-all-at-newline
** Bug watch added: Debian Bug tracker #747341 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341 ** Also affects: bash (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747341 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422795 Title: bash crashes often if inputrc contains revert-all-at-newline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1422795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504354] Re: Invalid memory access on ap_server_config_defines
I apparently forogt to actually attach the config fragment that reproduces the problem. ** Attachment added: "Configuration fragment for test case" https://bugs.launchpad.net/ubuntu/trusty/+source/apache2/+bug/1504354/+attachment/4497261/+files/ifdefine-test.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504354 Title: Invalid memory access on ap_server_config_defines To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1504354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504354] Re: Invalid memory access on ap_server_config_defines
apache 2 2.4.7-1ubuntu4.8 (in trusty-proposed) both passes the test case and fixes my original problem. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504354 Title: Invalid memory access on ap_server_config_defines To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1504354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1504354] Re: Invalid memory access on ap_server_config_defines
On Tue, 2015-10-13 at 11:00 +, Robie Basak wrote: > Fix -D[efined] or [d] variables lifetime across restarts. This > fixes incorrect processing of configuration files on reload (LP: > #1504354). > > If you let me know that you're happy with that text then I can just > change it when I upload - no need for you to submit another debdiff. That sounds fine; thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504354 Title: Invalid memory access on ap_server_config_defines To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1504354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504354] Re: Invalid memory access on ap_server_config_defines
** Patch added: "debdiff containing the upstream patch" https://bugs.launchpad.net/apache2/+bug/1504354/+attachment/4489268/+files/server_config_defines.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504354 Title: Invalid memory access on ap_server_config_defines To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1504354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504354] [NEW] Invalid memory access on ap_server_config_defines
Public bug reported:
A bug in the Apache2 HTTP server results in invalid memory references
in the ap_server_config_defines array after a graceful restart. This
can result in server config variables defined by means of the Define
directive appearing to be undefined after a graceful restart. This
can cause incorrect processing of configuration files. It can also
cause the server to exit due to invalid configuration, even though
the configtest prior to reload succeeded.
This bug was reported upstream against Apache 2.4.6 and 2.4.10. It
appears in the 2.4.7-1ubuntu4.7 found in trusty-proposed, but was
fixed in 2.4.12 and so does not appear in wily.
This is upstream PR 56008 and 57328.
[Test Case]
- apt-get install apache2
- Copy ifdefine-test.conf (attached) to /etc/apache2/sites-available
- a2ensite ifdefine-test.conf
- service apache2 restart
- Observe that http:///foo.html returns the default page
(same as http:///)
- service apache2 reload
- Examine /var/log/apache2/error.log; observe the warning message
"Config variable ${TEST2} is not defined"
- Observe that http:///foo.html now returns a 404.
With the bug fixed, the warning message will not appear, and the
foo.html URL will continue to work after the reload.
[Regression Potential]
Low.
The change is textually small (one line), but has a significant effect:
it ensures that a fresh copy is made of the array containing defined
variables each time the config file is read. Without this, on reloads
the original array (containing variables defined on the command line)
is modified directly, causing it to contain string pointers that will
become invalid when the configuration memory pool is released.
The patch only changes what happens when the configuration pool is
released, avoiding leaking memory references across successive reads
of the config file. As such, it is unlikely have any negative effect
on processing of the configuration, and extremely unlikely to have any
effect on operations once the server configuration has been read.
This change was applied upstream in December, 2014 and appears in the
upstream 2.4.12 release, which is in wily. The patch also appears in
2.4.10-10+deb8u2, which has been in Debian stable for about 5 weeks.
** Affects: apache2
Importance: Unknown
Status: Unknown
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: bz.apache.org/bugzilla/ #57328
https://bz.apache.org/bugzilla/show_bug.cgi?id=57328
** Also affects: apache2 via
https://bz.apache.org/bugzilla/show_bug.cgi?id=57328
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504354
Title:
Invalid memory access on ap_server_config_defines
To manage notifications about this bug go to:
https://bugs.launchpad.net/apache2/+bug/1504354/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445914] Re: Secure web socket proxy does not work in Apache 2.4.7
2.4.7-1ubuntu4.7 fixes my problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1445914 Title: Secure web socket proxy does not work in Apache 2.4.7 To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1445914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445914] Re: Secure web socket proxy does not work in Apache 2.4.7
Try this one. Note I omitted the Author tag. It's not clear to me that it's intended to name the author of the upstream patch, which in any case is available in the upstream bug, the upstream commit, and the debian/changelog entry. I myself have no authorship stake in this patch. Note that while the upstream commit also patches the CHANGES file, I've omitted that, because the addition is to a section (Changes with Apache 2.5.0) that doesn't exist in 2.4.7. This file doesn't appear to make it into any binary packages in any event. ** Patch added: "wstunnel-ssl-002.debdiff" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1445914/+attachment/4465275/+files/wstunnel-ssl-002.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1445914 Title: Secure web socket proxy does not work in Apache 2.4.7 To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1445914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445914] Re: Secure web socket proxy does not work in Apache 2.4.7
The upstream patch (see attached debdiff) corrects the problem for me, for an internal test case that is unfortunately too complex to share. ** Patch added: "debdiff containing the upstream patch" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1445914/+attachment/4460591/+files/wstunnel-ssl.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1445914 Title: Secure web socket proxy does not work in Apache 2.4.7 To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/1445914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367779] Re: [IMAPx] Fails to handle QUOTA response with no quotas
** Description changed: The IMAP QUOTA extension permits the list of resource-usage-limit tuples in an untagged QUOTA response to be empty (see RFC2087 section 5.1, which states "The list contains zero or more triplets". This happens when the server supports quotas, but no quota is set on a particular mailbox. However, e-d-s does not handle this case, and instead reports an error parsing the server response. This prevents opening the Properties dialog for folders in this state. In effect, this is a regression since raring. Support for the IMAP QUOTA extension was introduced in 3.7.3; prior to that, there was no quota support, but users were able to open the folder properties. This is reported upstream as GNOME #735200 (https://bugzilla.gnome.org/show_bug.cgi?id=735200) and has been fixed in 3.12 and later. However, trusty has 3.10.4, which upstream declined to fix. The attached patch applies the same fix to 3.10 which was accepted upstream for later versions. [Test Case] This requires an IMAP server which supports the QUOTA extension, allows some mailboxes to have no quota assigned even when the extension is enabled, and which (correctly) responds to QUOTA or QUOTAROOT requests relating to that mailbox by including an empty resource list. Current Cyrus IMAP is one example of such a server that meets this requirement. Naturally, it also requires a folder with no quota, and which is accessible to the user performing the test. The test, then, is simple: Right-click on the folder in question in Evolution, and select "Properties". When the test is successful, this opens a dialog showing settings and status information for the folder. - With the bug, instead an error is shown. + With the bug, instead an error is shown: + + >> Failed to open folder. + >> The reported error was "Error retrieving quota information: + >> expecting atom". [Regression Potential] Low. This is a relatively small patch to code which parses untagged QUOTA responses, plus a change in return code when a mailbox has no quota assigned. It affects only IMAP folders, and only on servers which support the QUOTA extension. It is possible that a bug could result in mis-parsing of QUOTA responses which are currently handled correctly, which would result in the same symptoms as this bug (but under different circumstances). Since the patch affects code which is used only to parse QUOTA responses, it cannot result in incorrect handling of other responses from the server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367779 Title: [IMAPx] Fails to handle QUOTA response with no quotas To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1367779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367779] Re: [IMAPx] Fails to handle QUOTA response with no quotas
** Description changed: The IMAP QUOTA extension permits the list of resource-usage-limit tuples in an untagged QUOTA response to be empty (see RFC2087 section 5.1, which states "The list contains zero or more triplets". This happens when the server supports quotas, but no quota is set on a particular mailbox. However, e-d-s does not handle this case, and instead reports an error parsing the server response. This prevents opening the Properties dialog for folders in this state. + In effect, this is a regression since raring. Support for the IMAP + QUOTA extension was introduced in 3.7.3; prior to that, there was no + quota support, but users were able to open the folder properties. + This is reported upstream as GNOME #735200 (https://bugzilla.gnome.org/show_bug.cgi?id=735200) and has been fixed in 3.12 and later. However, trusty has 3.10.4, which upstream declined to fix. The attached patch applies the same fix to 3.10 which was accepted upstream for later versions. + + [Test Case] + This requires an IMAP server which supports the QUOTA extension, allows + some mailboxes to have no quota assigned even when the extension is + enabled, and which (correctly) responds to QUOTA or QUOTAROOT requests + relating to that mailbox by including an empty resource list. Current + Cyrus IMAP is one example of such a server that meets this requirement. + + Naturally, it also requires a folder with no quota, and which is + accessible to the user performing the test. + + The test, then, is simple: Right-click on the folder in question in + Evolution, and select "Properties". When the test is successful, this + opens a dialog showing settings and status information for the folder. + With the bug, instead an error is shown. + + [Regression Potential] + Low. This is a relatively small patch to code which parses untagged + QUOTA responses, plus a change in return code when a mailbox has no quota assigned. It affects only IMAP folders, and only on servers + which support the QUOTA extension. It is possible that a bug could + result in mis-parsing of QUOTA responses which are currently handled + correctly, which would result in the same symptoms as this bug (but + under different circumstances). Since the patch affects code which is + used only to parse QUOTA responses, it cannot result in incorrect + handling of other responses from the server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367779 Title: [IMAPx] Fails to handle QUOTA response with no quotas To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1367779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1367779] [NEW] [IMAPx] Fails to handle QUOTA response with no quotas
Public bug reported: The IMAP QUOTA extension permits the list of resource-usage-limit tuples in an untagged QUOTA response to be empty (see RFC2087 section 5.1, which states "The list contains zero or more triplets". This happens when the server supports quotas, but no quota is set on a particular mailbox. However, e-d-s does not handle this case, and instead reports an error parsing the server response. This prevents opening the Properties dialog for folders in this state. This is reported upstream as GNOME #735200 (https://bugzilla.gnome.org/show_bug.cgi?id=735200) and has been fixed in 3.12 and later. However, trusty has 3.10.4, which upstream declined to fix. The attached patch applies the same fix to 3.10 which was accepted upstream for later versions. ** Affects: evolution-data-server Importance: Unknown Status: Unknown ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Patch added: "patch for e-d-s 3.10 to handle QUOTA responses with an empty resource lists" https://bugs.launchpad.net/bugs/1367779/+attachment/4200644/+files/imapx-empty-quota-3.10 ** Description changed: - The IMAP QUOTA extension permits the list of resource-usage-limit tuples in an - untagged QUOTA response to be empty (see RFC2087 section 5.1, which states "The - list contains zero or more triplets". This happens when the server supports - quotas, but no quota is set on a particular mailbox. + The IMAP QUOTA extension permits the list of resource-usage-limit tuples + in an untagged QUOTA response to be empty (see RFC2087 section 5.1, + which states "The list contains zero or more triplets". This happens + when the server supports quotas, but no quota is set on a particular + mailbox. - However, e-d-s does not handle this case, and instead reports an error parsing - the server response. This prevents opening the Properties dialog for folders in - this state. + However, e-d-s does not handle this case, and instead reports an error + parsing the server response. This prevents opening the Properties + dialog for folders in this state. - This is reported upstream as GNOME #735200 (https://bugzilla.gnome.org/show_bug.cgi?id=735200) - and has been fixed in 3.12 and later. However, trusty has 3.10.4, which upstream declined to fix. - The attached patch applies the same fix to 3.10 which was accepted upstream for later versions. + This is reported upstream as GNOME #735200 + (https://bugzilla.gnome.org/show_bug.cgi?id=735200) and has been fixed + in 3.12 and later. However, trusty has 3.10.4, which upstream declined + to fix. The attached patch applies the same fix to 3.10 which was + accepted upstream for later versions. ** Bug watch added: GNOME Bug Tracker #735200 https://bugzilla.gnome.org/show_bug.cgi?id=735200 ** Also affects: evolution-data-server via https://bugzilla.gnome.org/show_bug.cgi?id=735200 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1367779 Title: [IMAPx] Fails to handle QUOTA response with no quotas To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1367779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1204195] Re: OpenAFS Security Advisories 2013-0003 and 2013-0004
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204195 Title: OpenAFS Security Advisories 2013-0003 and 2013-0004 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/1204195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192874] Re: heap overflow while processing InclusiveNamespace PrefixList
Yes, the patch updates the package to 1.6.1-6. That actually seems appropriate to me in this case. The only code changes since 1.6.1-1 are the (four!) security patches in 1.6.1-6, only one of which is the one mentioned in this bug. Other changes relate only to packaging: - Update to debhelper v9 - Enable multiarch - Enable hardening build flags - A format change to the debian/copyright file In particular, the complex changes to build and maintain a symbols file mentioned in the changelog were completely reverted, and so do not appear here. I suppose one could argue that enabling multiarch has the potential to cause problems, but if that were the case, I think we'd have seen it by now, in Debian or in later Ubuntu releases. While I'm all for being conservative about what goes into security releases, IMHO in this case community is best served by getting the security fix out quickly (it's already been three weeks since upstream released the fix) and incidentally paving the way for promptly releasing any future fixes. Thus, I'd recommend abandoning any attempt to pull in only 95% of the changes since 1.6.1-1, and instead just sync 1.6.1-7 from Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192874 Title: heap overflow while processing InclusiveNamespace PrefixList To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xml-security-c/+bug/1192874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575458] Re: /etc/dhcp3/dhclient-exit-hooks.d/ntp breaks local NTP server (patch)
> The following patch fixes the problem by *not* replacing ntp servers with an address beginning with "127." No, it doesn't. It masks the problem by removing only servers with a name or address that starts with something other than a '1', followed by something other than a '2', followed by something other than a '7', followed by a dot. For example, with your patch, the following entries are no longer removed: server 0.ubuntu.pool.ntp.org server 1.ubuntu.pool.ntp.org server 2.ubuntu.pool.ntp.org server 3.ubuntu.pool.ntp.org server 127.1.2.3 server clock-1.cs.cmu.edu ... but this is: server ntp.ubuntu.com Unfortunately, this means that several of the server entries in the default /etc/ntp.conf are no longer removed. As a result, an unmodified machine booting on a network where DHCP provides a list of local NTP servers gets the local servers plus four from pool.ntp.org. A better answer here would be to find a proper solution to #374896, such that locally-added entries can be retained when desired (and only then!), and use that for refclock entries (127.*) as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/575458 Title: /etc/dhcp3/dhclient-exit-hooks.d/ntp breaks local NTP server (patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/575458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857663] Re: cups crashes on SIGHUP if printer classes are defined
This was never in precise; it was fixed upstream in 1.4.4, so doesn't affect anything newer than lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857663 Title: cups crashes on SIGHUP if printer classes are defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/857663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965662] Re: pam-auth-update conflict resolution shouldn't warn
"need" is an awfully strong word. As documented, the resolution mechanism compares priorities on the affected modules to determine which one to use in case of a conflict. That's what guarantees the result is what you want, or at least what the package maintainers wanted the default behavior to be when those modules were selected together. In situations where such a conflict can be resolved automatically through the use of priorities, there is no reason to require user interaction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965662 Title: pam-auth-update conflict resolution shouldn't warn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/965662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663319] Re: libpam-heimdal does not work on Maverick and Natty
That's all very nice, but what about the underlying problem? The problem is not fixed; it is merely masked. See my comments #6, 7, 8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/663319 Title: libpam-heimdal does not work on Maverick and Natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/663319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663319] Re: libpam-heimdal does not work on Maverick
As noted, this is really due to a backward-incompatible ABI change in libasn1-8-heimdal ** Package changed: libpam-heimdal (Ubuntu) => heimdal (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/663319 Title: libpam-heimdal does not work on Maverick -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663319] Re: libpam-heimdal does not work on Maverick
It's been suggested that I point out the only viable solution here is to reintroduce the missing symbols in libasn1.so.8. While it would have been reasonable to bump the soname version before releasing the backward-incompatible library in the first place, the only way now to fix the problem without creating new problems for more recently built binary packages is to release a libasn1-8-heimdal in which libasn1.so.8 contains both old and new symbols. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/663319 Title: libpam-heimdal does not work on Maverick -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663319] Re: libpam-heimdal does not work on Maverick
The symbol mentioned in the original error message (oid_id_pkcs3_rc2_cbc) comes from libasn1.so.8. The actual cause of this problem is that that symbol, along with several others, were renamed (a backward-incompatible ABI change) without a corresponding change in soname. Since libkrb5.so.25 depends (indirectly) on this library, this means that _any_ package built against Heimdal on a Lucid system will fail to work on Maverick or Natty. The actual problem is in heimdal itself; libpam-heimdal just happens to be an example of such a package that is still present after a Lucid system is upgraded, because it does not (yet) appear in Maverick or Natty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/663319 Title: libpam-heimdal does not work on Maverick -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
