8.2 and 8.3 are unaffected. I'll let Athos chime in with the steps
necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054621
Title:
Fix PHP crashes due to accessing dangling pointers
To
Hi Athos,
Looks great, and thanks for your help! Let me know if I can do anything
else to help with this or future bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054621
Title:
PHP crashes on
** Description changed:
SRU Justification
[ Impact ]
Invoking reflection via the observer API on a class with an attribute
annotation causes a dangling pointer and segmentation fault. Certain PHP
extensions may register an observer of an attribute instantiation using
reflection.
@alexmurray - The debdiff for Groovy is identical to the one from Focal
(same source package version). Let me know if you need a distinct
debdiff with the release pocket (groovy-security) identified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Patch for Focal
** Patch added: "Patch for Focal"
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+attachment/5438836/+files/1-ntp_4.2.8p12+dfsg-3ubuntu5.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@alexmurray - Yes, I'll work on it this week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891953
Title:
CVE-2019-8936
To manage notifications about this bug go to:
Hi Alex, thanks very much for fixing that loose end in the changelog and
for sponsoring this fix. I can produce them for the other releases as
well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "Debdiff for Bionic"
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1891953/+attachment/5402291/+files/1-4.2.8p10+dfsg-5ubuntu7.3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-8936
** Information type changed from Public 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/1891953
Title:
)
Importance: Undecided
Assignee: Brian Morton (rokclimb15)
Status: In Progress
** Changed in: ntp (Ubuntu)
Assignee: (unassigned) => Brian Morton (rokclimb15)
** Changed in: ntp (Ubuntu)
Status: New => In Progress
--
You received this bug notification becau
Requires security backport for Bionic only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891953
Title:
CVE-2019-8936
To manage notifications about this bug go to:
Confirmed problem on Ubuntu 16.04 host running 16.04 container with a
packaged version of Proxysql2. Changing PrivateDevices to "no" allows
the service to start.
```
[Unit]
Description=High Performance Advanced Proxy for MySQL
After=network.target
[Service]
Type=forking
RuntimeDirectory=proxysql
Ah, that makes sense.
On Mon, Dec 10, 2018 at 6:50 AM Andreas Hasenack
wrote:
> > However, I would prefer that someone with more Apache experience
> reviewed the fix.
>
> Right, that was actually my (very unclear, sorry) point when I commented
> on upstream's interest in this, since they would
Andreas,
I think patching this in Ubuntu only rather than upstream makes sense for
the reasons you've outlined. However, I would prefer that someone with more
Apache experience reviewed the fix.
Thanks,
Brian
On Fri, Dec 7, 2018 at 10:21 AM Christophe Meron <1630...@bugs.launchpad.net>
wrote:
Verified successfully in 1.3.5a-1ubuntu0.1
Command: MLSD
Status: Data connection established.
Reply: 150 Opening BINARY mode data connection for MLSD
Listing:
modify=20181119215133;perm=fle;type=pdir;unique=9AU7A5;UNIX.group=0;UNIX.mode=0755;UNIX.owner=0;
..
Reply: 226 Transfer complete
Status:
Thanks for the clarification Christophe. So it sounds like the fix
addresses the problem. I think the patch in that PPA should get more
review from an Apache developer before it is used further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Christophe,
Sorry for the delay. Apparently I wasn't getting these notifications for
some reason. I'm not well versed enough with Docker to set up an
environment to reproduce. I use LXD almost exclusively. Does the crash
occur in your Docker container with my patched PPA build? Andreas seems
** Description changed:
+ [Impact]
+
+ * A bug exists in Proftpd version 1.3.5a. which causes FTP sessions to
+ fail or timeout with strict clients
+
+ * The package, as published in LTS, does not comply with the FTP
+ protocol
+
+ * Ported upstream patch and test changes
+
+ [Test Case]
+
Hi Simon,
Thanks for your notes. I've attached a new patch and I'm adding SRU
justification to the description now.
** Patch removed: "Xenial debdiff"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1613737/+attachment/5017207/+files/proftpd-dfsg_1.3.5a-1build2.debdiff
**
** Attachment added: "Test log after patch"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1613737/+attachment/5017210/+files/goodtest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Test log after patch"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1613737/+attachment/5017209/+files/goodtest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debdiff attached for Xenial along with before and after patch test logs
from ftptest.net
** Patch added: "Xenial debdiff"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1613737/+attachment/5017207/+files/proftpd-dfsg_1.3.5a-1build2.debdiff
--
You received this bug notification
Test log before patch
** Attachment added: "Test log before patch"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1613737/+attachment/5017208/+files/badtest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: python2.7 (Ubuntu Xenial)
Assignee: (unassigned) => Brian Morton (rokclimb15)
** Changed in: python2.7 (Ubuntu)
Assignee: Brian Morton (rokclimb15) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
https://github.com/proftpd/proftpd/pull/152
** Changed in: proftpd-dfsg (Ubuntu)
Assignee: (unassigned) => Brian Morton (rokclimb15)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613737
Ti
*** This bug is a duplicate of bug 1246245 ***
https://bugs.launchpad.net/bugs/1246245
** This bug has been marked a duplicate of bug 1246245
proftpd service fails to restart (including via logrotate)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1246245 ***
https://bugs.launchpad.net/bugs/1246245
** This bug has been marked a duplicate of bug 1246245
proftpd service fails to restart (including via logrotate)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1613737 ***
https://bugs.launchpad.net/bugs/1613737
** This bug has been marked a duplicate of bug 1613737
Proftpd - MLSD lines not properly terminated with CRLF
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tests are here:
https://github.com/latchset/jwcrypto/pull/66/commits/b2b66b53bc0df72eb761959fe39700451803d8ab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717356
Title:
CVE-2016-6298
To manage
Hi Christophe,
Thanks for your hard work on this one. Unfortunately I can't reproduce
the crash with your test. I even raised the file size to 500M, but still
nothing.
Is there anything I could be missing? Any PPA packages with newer
versions of PHP or other Apache modules loaded?
17.04 and 17.10 are not affected since they publish the fixed version
0.3.2. 16.04 appears to be affected, but the code is significantly
different. I've requested info from the source project owner to test my
proposed patch for 16.04.
--
You received this bug notification because you are a
Message Attack (MMA).
https://people.canonical.com/~ubuntu-
security/cve/2016/CVE-2016-6298.html
** Affects: python-jwcrypto (Ubuntu)
Importance: Undecided
Assignee: Brian Morton (rokclimb15)
Status: In Progress
** Information type changed from Private Security to Public
Hi Christophe,
That is excellent. Could you please provide me with a test case that
previously reproduced the crash? I'd like to try to boil it down to
something simple. I will need to demonstrate that it can be reproduced
easily and consistently to get an SRU approved. There aren't a lot of
Fantastic news! My biggest concern now is that my monkey-patch has
introduced some unexpected behavior since we don't try to dereference
sbh on each read request (only when the connection state is suspended).
This is based on my own observation of the problem rather than an
upstream patch since
Hi Christophe,
Let's try something completely different. I have a new build uploaded
for testing.
Thanks,
Brian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630413
Title:
segfault in
Hi Christophe,
I believe I've narrowed down the problem to one fixed in these two changesets:
https://github.com/apache/httpd/commit/59eea59c4be383d004e92fa63b57b995e7a8ef01
https://github.com/apache/httpd/commit/285e67883e396f97dc3aad50d9dc345f15220827
The latter only applies to 2.4.10 since it
Thanks for the core dump and bt Christophe. After a bit of research, I
believe this is a race condition present in 2.4.7 which was subsequently
patched, and then the patch refactored when the suspend/resume hooks
were added in 2.4.10. The fix in 2.4.7 seems simply enough (just move
c->sbh = NULL
Adam,
Thanks for the idea, that's helpful and makes sense. I checked the debian
build logs for libapache2-mod-gnutls, p11-kit, softhsm2, and glibc. They're
all built with stack-protector-strong.
On Tue, May 30, 2017 at 3:39 PM, Adam Conrad wrote:
> The difference between
An excellent question/point. That should probably get hashed out on the
upstream BZ first. The discussion about it was very minimal. I'll get on
there and poke at that issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't think it is an actual incompatibility since the util function
for copying those values takes into consideration the size of the dst
buffer. As long as it is being lengthened, I think it's OK. It would be
a problem if we were reducing it and src were larger than dst.
#define
Hi Robie,
I do not know for certain. One user on the upstream bug mentions it
can't be backported because of an API compat issue, but if there's one
present I'm sure not seeing it. The define is entirely contained within
that header file. The only thing I would think it could affect would be
Had the same error, but commenting/adjusting LimitNPROC didn't fix the
issue. Ultimately I had to make the container unconfined by AA and
privileged to get openvpn to start.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: apache2 (Debian)
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/1668474
Title:
AH00526 when using long ProxyPass worker name
To manage
Hi Robie, this fix is in Apache SVN trunk but isn't in upstream stable
2.4 release branch yet so all Ubuntu versions will be affected. In
addition, no such patch exists in Debian source.
https://anonscm.debian.org/cgit/pkg-
apache/apache2.git/tree/modules/proxy/mod_proxy.h#n350 and
bmorton@maui:~$ sudo apt-get install proftpd-basic/trusty-proposed
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '1.3.5~rc3-2.1ubuntu2.2' (Ubuntu:14.04/trusty-proposed
[amd64]) for 'proftpd-basic'
Suggested packages:
openbsd-inetd
Patch attached for trusty. Unsure how to generate a debdiff in this
case.
** Patch added: "Patch for trusty"
https://bugs.launchpad.net/apache2/+bug/1668474/+attachment/4827987/+files/mod-proxy-worker-name-size.patch
--
You received this bug notification because you are a member of Ubuntu
** Changed in: apache2 (Ubuntu)
Assignee: (unassigned) => Brian Morton (rokclimb15)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668474
Title:
AH00526 when using long ProxyPass worker n
Public bug reported:
When using a long ProxyPass worker name such as unix:///var/php-
fpm/146527084714328.sock|fcgi://localhost/home/mysite/domains/subdomain.com/public_html/$1
Apache issues the fatal error AH00526 and refuses to proceed during
reload. This is a typical configuration generated by
As a workaround for trusty, you can use unix:///run/php-fpm/php-
fpm.sock|fcgi://127.0.0.1:9000/srv/http/ (notice the triple slash on the
unix socket). Only problem then is the length of the variable
https://bz.apache.org/bugzilla/show_bug.cgi?id=53218
** Bug watch added: bz.apache.org/bugzilla/
Seth, sorry about that. I think I was moving a little too quickly on
that one. Corrected one attached.
** Patch removed: "Debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/libssh2/+bug/1664812/+attachment/4820419/+files/libssh2_1.4.3-2ubuntu0.1.debdiff
** Patch added: "Debdiff
** Patch added: "Debdiff for precise"
https://bugs.launchpad.net/ubuntu/+source/libssh2/+bug/1664812/+attachment/4820426/+files/libssh2_1.2.8-2ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debdiff for trusty
** Patch added: "Debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/libssh2/+bug/1664812/+attachment/4820419/+files/libssh2_1.4.3-2ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No problem, just let me know if they need different versioning because
of the potential conflict. I plan to produce one for trusty shortly. At
this point, is the team encouraging CVE fixes for precise? This is not
easy to exploit, so it might not be worth the review/publishing time.
--
You
Debdiff for xenial
** Patch added: "Debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/libssh2/+bug/1664812/+attachment/4819155/+files/libssh2_1.5.0-2ubuntu0.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tweaked this debdiff changelog for Zesty upload. Same package version as
Yakkety.
** Patch added: "Debdiff for zesty"
https://bugs.launchpad.net/ubuntu/+source/libssh2/+bug/1664812/+attachment/4819154/+files/libssh2_1.7.0-1ubuntu0.1.zesty.debdiff
--
You received this bug notification
** Changed in: libssh2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664812
Title:
CVE-2016-0787
To manage notifications about this bug go to:
Debdiff for Yakkety
The vuln has no specific known attack methods so there is no public
exploit available. Package tests have passed and I used a somewhat
unusual method to explicitly regression test. Package php-ssh2 depends
on libssh2.
'diffie-hellman-group1-sha1'
);
// Make our connection
** Information type changed from Public 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/1664812
Title:
CVE-2016-0787
To manage notifications about this bug go to:
;bits/bytes
confusion bug."
** Affects: libssh2 (Ubuntu)
Importance: Undecided
Assignee: Brian Morton (rokclimb15)
Status: New
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2016-0787
** Changed in: libssh2 (Ubuntu)
Assignee: (unassigned) =>
Revised debdiff with correct changelog message.
** Patch added: "Debdiff for trusty with corrected changelog"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1246245/+attachment/4818195/+files/proftpd-dfsg_1.3.5~rc3-2.1ubuntu3.debdiff
** Patch removed: "Debdiff for trusty"
Attaching debdiff for trusty. Editing bug to add SRU justification.
** Patch added: "Debdiff for trusty"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1246245/+attachment/4817938/+files/proftpd-dfsg_1.3.5~rc3-2.1ubuntu3.debdiff
** Description changed:
+ [Impact]
+
+ *
** Changed in: proftpd-dfsg (Ubuntu)
Assignee: (unassigned) => Brian Morton (rokclimb15)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246245
Title:
proftpd service fails to rest
Hi Thomas,
Good info, thanks. It's definitely a possibility, but I'm having a hard
time explaining how that package could be responsible when it is synced
with Sid as well and the configure strings in the build logs appear to be
the same. I also tried a build from upstream source with the same
I don't see evidence of this error in the amd64 build log at
https://launchpadlibrarian.net/298782129/buildlog_ubuntu-zesty-amd64
.location-service_3.0.0+16.10.20160912-0ubuntu2_BUILDING.txt.gz.
However, the package does FTBFS due to this bug
Could you please post your libvirt config file for the domain?
Specifically, I'd like to know if it has the apic feature enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637835
Title:
Zesty
Ref https://bugs.launchpad.net/ubuntu/+source/python3.5/+bug/1650202 and
https://github.com/python/typing/commit/7baf6fe2a6d96ab09c807aac174650baa35d15dd
Optional returns a Union, which can't be subclassed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is expected behavior from upstream changes.
https://github.com/python/typing/commit/7baf6fe2a6d96ab09c807aac174650baa35d15dd
Optional is shorthand for Union, and Union cannot be subclassed. This
behavior "worked" before, but was undefined and returned unpredictable
results.
** Changed in:
Tried building openssl 1.1 to match Debian sid, as well as latest
apache2 and gnutls. All still segfault on i386 during this test. Out of
ideas at this point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
root@checkinstall-bug-trusty:~# apt-get install checkinstall
root@checkinstall-bug-trusty:~# apt-get source haproxy
root@checkinstall-bug-trusty:~# cd haproxy*
root@checkinstall-bug-trusty:~/haproxy-1.5.14# mkdir -p etc/haproxy
root@checkinstall-bug-trusty:~/haproxy-1.5.14# touch
Hi Brian,
Thanks for taking the time on this really old bug. Will this work?
root@checkinstall-bug-trusty:~# apt-get source haproxy checkinstall
root@checkinstall-bug-trusty:~# cd haproxy*
root@checkinstall-bug-trusty:~/haproxy-1.5.14# mkdir -p etc/haproxy
According to the Debian maintainer this does not occur in unstable on
i386. Both apache2 and libgnutls30 are newer in unstable, so that could
be related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Correction, it still segfaults on test 24 after the string format issues
are fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597450
Title:
mod-gnutls FTBFS: test failure: apache2 seg fault
Using latest deps in proposed Apache no longer segfaults on i386. FTBFS
persists due to -Werror=format in the build and a few format/type issues
that are easily fixed. Beyond that, test 24 still fails now with an
error about the PKCS11 URL format which needs further investigation.
0.8.1 fixes the
Bug has been fixed upstream http://bugtrack.izto.org/show_bug.cgi?id=35
** Bug watch added: izto #35
http://bugtrack.izto.org/show_bug.cgi?id=35
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Zesty 0.8.0-1 is the current FTBFS. I was able to progress the debugging
a bit and something is scribbling on the stack. The problem I'm
experiencing is gdb disables breakpoints in the shared lib I need to
examine the stack canary address.
Starting program: /usr/sbin/apache2 -X -f
Hi Ian, can you raise ulimit, add CoreDumpDirectory, and install
apache2-dbg (will restart to make prior two changes effective)? If you
make CoreDumpDirectory /tmp, make sure to move your core dump out of the
way before you reboot.
https://httpd.apache.org/dev/debugging.html#crashes
Then you'll
0.7.5 was removed from yakkety-proposed, but the FTBFS continues in
Zesty. Here's a backtrace and disassembly on i386. If anyone has ideas,
I'd appreciate them.
** Tags added: zesty
** Attachment added: "gdb bt of core dump"
This is interesting since the bug was fixed in 1.6-dev2.
https://github.com/haproxy/haproxy/commit/4cd477f3721f6a3fe7cf55ae729388bf7f279331
There are two curious conditions in the code:
if (s->admin & SRV_ADMF_MAINT)
return;
if (s->state == SRV_ST_STARTING || s->state == SRV_ST_RUNNING)
Nominating this for wontfix since security support has ended for
releases with haproxy >= 1.5 and <= 1.5.7. Everything earlier doesn't
have SSL support built-in, and everything later is unsupported or has
received the upstream fix. The solution is to upgrade to trusty and use
backports or upgrade
Debdiff for Trusty and all newer releases.
** Patch added: "Debdiff for trusty and newer"
https://bugs.launchpad.net/debian/+source/checkinstall/+bug/1304760/+attachment/4791416/+files/checkinstall_1.6.2-4ubuntu2.debdiff
--
You received this bug notification because you are a member of
After further research, the regression has been reported to Debian and a
patch is attached to that report. It does not appear to have been
applied. Debdiff attached for precise.
** Patch added: "Debdiff for precise"
://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781169
** Also affects: checkinstall (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781169
Importance: Unknown
Status: Unknown
** Changed in: checkinstall (Ubuntu)
Assignee: (unassigned) => Brian Morton (rokclimb15)
--
Attached is a debdiff for trusty. If someone could please review and
provide feedback, I'll produce additional ones for precise, xenial,
yakkety, and zesty
** Patch added: "Debdiff of modified upstream patch for trusty"
** Changed in: python2.7 (Ubuntu)
Assignee: (unassigned) => Brian Morton (rokclimb15)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512068
Title:
Python ctypes.util , Shell Inject
Adding reworked patch for trusty that fixes an API issue with returning
the error code/message and is more minimal and appropriate for a
backported fix.
** Patch removed: "Debdiff of upstream patch for precise"
Adding reworked patch for precise that fixes an API issue with returning
the error code/message and is more minimal and appropriate for a
backported fix.
** Patch added: "Debdiff of upstream patch for precise"
Attaching debdiff of upstream patch for precise. Tested in same manner
as trusty.
** Patch added: "Debdiff of upstream patch for precise"
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1462311/+attachment/4787127/+files/proftpd-dfsg_1.3.4a-2.debdiff
--
You received this bug
Attaching debdiff of upstream patch for trusty package. Precise is also
vulnerable, so I will mark that as well while I work on that next.
My primary test before/after patch:
220 ProFTPD 1.3.5rc3 Server (Debian) [:::10.129.53.2]
USER bmorton
331 Password required for bmorton
PASS ***
230
Makes sense to me, thanks for looking into that!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636617
Title:
lxc set device root size fails silently when out of space
To manage notifications
Public bug reported:
On 16.04.1, use lxd init with default responses (zfs, loopback, 10G).
Create container with lxc launch. Attempt to resize container root to
20G (larger than loopback file).
lxc set device root size 20G reports no error, but the container still
has a 1.1G root as shown by lxc
IMHO, this was a horribly bad decision upstream. If you've restricted
your incoming NRPE source to a trusted one with UFW or similar, this is
a perfectly safe thing to do and helps centrally manage lots of
parameters. I think a default arg of 0 was enough to keep a safe
config. Users who choose
IMHO, this was a horribly bad decision upstream. If you've restricted
your incoming NRPE source to a trusted one with UFW or similar, this is
a perfectly safe thing to do and helps centrally manage lots of
parameters. I think a default arg of 0 was enough to keep a safe
config. Users who choose
I suspect there isn't a code change here, but rather a difference in the
way Ubuntu is presenting its mount points. The plugin tries to
enumerate and check all mounts. A better use might be to add the actual
mount points to be monitored with -p
/usr/lib/nagios/plugins/check_disk -w '20%' -c
strace confirms that check_disk on 12.04 doesn't check
/sys/kernel/debug/tracing
Not having any luck tracking down a code change in the monitoring-
plugins github repo. I wonder if this is a change in a dependent lib
instead.
Here's a workaround
sudo chown root:root
strace confirms that check_disk on 12.04 doesn't check
/sys/kernel/debug/tracing
Not having any luck tracking down a code change in the monitoring-
plugins github repo. I wonder if this is a change in a dependent lib
instead.
Here's a workaround
sudo chown root:root
I suspect there isn't a code change here, but rather a difference in the
way Ubuntu is presenting its mount points. The plugin tries to
enumerate and check all mounts. A better use might be to add the actual
mount points to be monitored with -p
/usr/lib/nagios/plugins/check_disk -w '20%' -c
Bug is fixed in Wily due to a resync with upstream.
http://changelogs.ubuntu.com/changelogs/pool/universe/z/zsnes/zsnes_1.510+bz2-8/changelog
Also, they added a debug package, which is great news.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This worked for me:
ssh -v admin@172.16.3.253 -o KexAlgorithms=diffie-hellman-group14-sha1
source:
http://stackoverflow.com/questions/25341773/cisco-ssh-key-exchange-
fails-from-ubuntu-14-04-client-dh-key-range-mismatch
--
You received this bug notification because you are a member of Ubuntu
This worked for me:
ssh -v admin@172.16.3.253 -o KexAlgorithms=diffie-hellman-group14-sha1
source:
http://stackoverflow.com/questions/25341773/cisco-ssh-key-exchange-
fails-from-ubuntu-14-04-client-dh-key-range-mismatch
--
You received this bug notification because you are a member of Ubuntu
I did not file a new bug only because it was a system that I was sending
off for production use and I stuck with the non-LVM RAID for
reliability. I could attempt reproduction on another system, but I'm
pretty sure it will happen on any system with the steps I described.
Note that I didn't
1 - 100 of 132 matches
Mail list logo