Revision 108 has been merge upstream.
The proposal to merge lp:~benoit-guyard/ltsp/libpam-sshauth into
lp:~ltsp-upstream/ltsp/libpam-sshauth has been updated.
Status: Approved => Merged
==
$ bzr log -r 108
--
revno: 108
committer: Benoît Guyard
branch nick:
** Description changed:
- It as been brought to my attention that libpam-sshauth (version >=0.3-1)
- have dropped support for publickey authentication.
+ [Impact]
+ libpam-sshauth v0.1-1 (shipped with precise) used to support publickey
+ authentication with ssh-agent.
+
+ New version of this
debdiff for Trusty (0.3.1-2)
** Patch added: "trusty_libpam-sshauth_0.3.1-2"
https://bugs.launchpad.net/ubuntu/+source/libpam-sshauth/+bug/1507798/+attachment/4524163/+files/lp1507798_trusty_0.3.1-2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Patch removed: "lp1507798_xenial_0.3.1-1ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/libpam-sshauth/+bug/1507798/+attachment/4524151/+files/lp1507798_xenial_0.3.1-1ubuntu1.debdiff
** Patch removed: "lp1507798_trusty_0.3.1-2"
** 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/1507798
Title:
libpam-sshauth dropped support for publickey authentication
To manage notifications about this bug go
debdiff for Trusty (0.3.1-2)
** Patch added: "lp1507798_trusty_0.3.1-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libpam-sshauth/+bug/1507798/+attachment/4524152/+files/lp1507798_trusty_0.3.1-2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
debdiff for Xenial (0.3.1-1ubuntu1)
** Patch added: "lp1507798_xenial_0.3.1-1ubuntu1"
https://bugs.launchpad.net/ubuntu/+source/libpam-sshauth/+bug/1507798/+attachment/4524151/+files/lp1507798_xenial_0.3.1-1ubuntu1.debdiff
--
You received this bug notification because you are a member of
Since the "libpam-sshauth" package is a sync from Debian, I have
reported a bug in order to apply the patch in Debian too:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805879
** Changed in: libpam-sshauth (Ubuntu Trusty)
Importance: Undecided => Low
** Changed in: libpam-sshauth (Ubuntu
The package in "Xenial" doesn't build without adding in debian/control
- Build-Depends: debhelper (>= 9), libssh2-1-dev, libpam0g-dev | libpam-dev,
dh-autoreconf, pkg-config
+ Build-Depends: debhelper (>= 9), libssh2-1-dev, libpam0g-dev | libpam-dev,
dh-autoreconf, pkg-config, zlib1g-dev
** Bug watch removed: Debian Bug tracker #767690
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767690
** Description changed:
+ [Impact]
+
+ Prevents deployment of TPM
+
+ Error output :
+
+ Setting up trousers (0.3.11.2-1) ...
+ * Starting Trusted Computing daemon tcsd [fail]
+
** Changed in: trousers (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: trousers (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: trousers (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification be
Could you please try this hotfix package of trousers. This will help
determine if the patch fix the problem.
Instructions
---
$ sudo add-apt-repository ppa:slashd/lp1484740
$ sudo apt-get update
$ sudo apt-get install trousers=0.3.11.2-1ubuntu1+hf20160806lp1484740 -y
---
Eric
** Changed in:
Additionally, to continue my previous comment
The new if statement is also looking for the existence of /dev/tmp*
device then do the "udevadm --version command" prior to perform an
udevadm task, so this condition will only succeed if TPM device and
udevadm is found on the system.
--
You
Explanation :
The bug is found in debian/trouser.postinst at line :19[1].
It tries to perform a "pidof udevd" on a machine where it is "systemd-udevd".
Because "pidof udevd" return nothing, than the if statement fails.
As mentioned, above by Edmond, changing the from "pidof udevd" to "pidof
** Description changed:
[Impact]
- Prevents deployment of TPM
+ This leaves the trousers package in a half-config state, prevents
+ deployment of TPM.
Error output :
Setting up trousers (0.3.11.2-1) ...
* Starting Trusted Computing daemon tcsd [fail]
invoke-rc.d: initscript
** Changed in: trousers (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484740
Title:
14.04.2 LTS trousers version 0.3.11.2-1 fa
** Changed in: trousers (Ubuntu)
Importance: Undecided => Low
** Changed in: trousers (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484740
Title:
14.04.2
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1484740
Title:
14.04 trousers version 0.3.11.2-1 fails to start with TPM device
To manage notifications about
Here's a positive feedback for my hotfix package
It has been brought to my attention :
---
That appears to have done the trick. trousers installed cleanly with this
package and opencryptoki & tpm-tools installed normally from our local mirror
after that.
# APT output :
Selecting
Patch: lp1484740_trusty.debdiff
** Patch added: "lp1484740_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1484740/+attachment/4680531/+files/lp1484740_trusty.debdiff
** Tags added: sts
** Tags added: verification-needed
--
You received this bug notification
** Tags removed: verification-needed-wily
** Tags added: verification-done-wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581169
Title:
kernel panic (General protection fault) on module hpsa
sshuttle on Xenial and late does support Python 3.5, include the
upstream commit :
ba1cf58 Add Python 3.5 support.
Introduced upstream in branch : v0.73~32
Eric
** Description changed:
- sshuttle package implementation doesn't support Python 3.5 on Trusty and
- Wily.
+ sshuttle package
Public bug reported:
sshuttle package implementation doesn't support Python 3.5 on remote
host running Xenial and late from a machine <= Wily release.
This cause the connection to fail if the connection is negotiated from a
Precise, Trusty or Wily machine and if the remote host is running Xenial
Xenial (16.04) by default comes only with python3 (Python 3.5)
installed.
The workaround is to install python 2.7 on the remote host using Xenial.
$ sudo apt-get install python -y
and then sshuttle work just fine
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Note that sshuttle package found on Xenial and late does support Python
3.5 as it include the following upstream commit --> ba1cf58 Add Python
3.5 support, that was first introduced upstream in branch : v0.73~32.
Eric
--
You received this bug notification because you are a member of Ubuntu
I'm currently investigating this bug..
Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767690
Eric
** Bug watch added: Debian Bug tracker #767690
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767690
--
You received this bug notification because you are a member of Ubuntu
I'm currently investigation this bug...
Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739485
Eric
** Bug watch added: Debian Bug tracker #739485
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739485
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- 14.04.2 LTS trousers version 0.3.11.2-1 fails to start
+ 14.04 trousers version 0.3.11.2-1 fails to start when TPM device
** Summary changed:
- 14.04 trousers version 0.3.11.2-1 fails to start when TPM device
+ 14.04 trousers version 0.3.11.2-1 fails to start with TPM
Adding a screen capture.
** Attachment added: "error_screenshot"
https://bugs.launchpad.net/ubuntu/+source/conjure-up/+bug/1586226/+attachment/4671028/+files/conjure-up.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using conjure-up from the ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1586226
Title:
Oops during the pre-processing tasks
To manage notifications about this bug go to:
Public bug reported:
Oops, there was a problem with your install:
Reason:
There was an error during the pre processing phase.
--
Exception in ev.run():
Traceback (most recent call last):
File "/usr/share/conjure-up/ubuntui/ev.py", line 83, in run
cls.loop.run()
File
I found the problem.
For some reason .config/lxc was own by root:root
Maybe because I first tried to run conjure-up as root ?
syslog:May 26 21:59:47 openstack: [WARNING] error: cannot
read config file: open /home//.config/lxc/config.yml: permission
denied
It is now working since I changed the
** Description changed:
It has been brought to my attention :
"Contrail deployment requires Trusty kernel 3.13.X
- kernel 3.13.X has an older version of the driver, which disregards
+ kernel 3.13.X has an older version of the i40e driver, which disregards
packets with vlan ids.
It has been brought to my attention that the package has been tested on
an affected system and the test was successful.
Eric
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: openldap (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593378
Title:
crash in slap_bv2ad using repeated tags
To manage notifications
The user that originally reported the issue on Ubuntu package have tested a
"Test package".
The "Test package" I have builded can be found here : ppa:slashd/fix1593378.
Users feedback :
"We tested the hotfix and looks like it works, the sldap on the CIC with
the fix didn`t crash."
Eric
**
** Description changed:
+ [Impact]
+
+ The effect of the bug on users is that the program (slapd) terminated
+ with signal SIGSEGV, Segmentation fault when ldapsearch tries to query
+ using multiple language tags.
+
+
+ GDB output:
+ ...
+ Core was generated by `/usr/sbin/slapd -h ldap://:389
I believe this upstream commit have some good chance to fix the problem.
i40e: Fix a port VLAN configuration bug
If a port VLAN is set for a given virtual function (VF) before the VF
driver is loaded then a configuration error results in which the port
VLAN is ignored when the VF driver is
Public bug reported:
It has been brought to my attention :
"Contrail deployment requires Trusty kernel 3.13.X
kernel 3.13.X has an older version of the driver, which disregards
packets with vlan ids.
This driver work as expect in Kernel 4.4.X (Xenial) but not 3.13.X
(Trusty).
This is a
Here's the debdiff for Trusty which is a cherry picked patch from
upstream VCS.
** Patch added: "lp1593378_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1593378/+attachment/4687422/+files/lp1593378_trusty.debdiff
** Changed in: openldap (Ubuntu Trusty)
Public bug reported:
Core was generated by `/usr/sbin/slapd -h ldap://:389 ldap://:389/
ldapi:/// -g o'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __strncasecmp_l_ssse3 () at ../sysdeps/x86_64/multiarch/../strcmp.S:210
210 ../sysdeps/x86_64/multiarch/../strcmp.S: No
I think this upstream commit could be a possible candidate to fix that
issue :
commit 0659ef45d486b5daaafc020cb67b561a8029036d
Author: Howard Chu
Date: Thu Sep 18 00:33:33 2014 +0100
ITS#7941 fix for repeated tags
Make sure ntags isn't incremented if we're
** Changed in: openldap (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593378
Title:
crash in slap_bv2ad using repeated tags
To manage notifications
line #272 checks for duplication and jumps to the done label (line #294)
when a duplicate is found.
The code increases 'ntags' without filling in the tags struct with values.
In later iterations this could lead to copying and using uninitialised memory.
--
You received this bug notification
HOWTO reproduce the problem:
* Have a corosync/pacemaker cluster with libqb version <=0.16.0.real-1ubuntu4
* You need sequentially start/stop Corosync/Pacemaker for some amount of times
to trigger the issue.
(Note : PID of pacemaker must be >9 to trigger this issue)
--
You received this
Patch for Wily
** Patch added: "lp1595627_wily.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1595627/+attachment/4689261/+files/lp1595627_wily.debdiff
** Tags added: patch sts sts-sponsor sts-sru ubuntu-sponsors
** Changed in: libqb (Ubuntu Trusty)
Status: Confirmed
Patch for Trusty
** Patch added: "lp1595627_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libqb/+bug/1595627/+attachment/4689260/+files/lp1595627_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem is then length of CONNECTION_DESCRIPTION field.
filename: lib/ipc_int.h
#define CONNECTION_DESCRIPTION (16)
When both corosync and pacemaker has PID greater than 9 and the file
descriptor >= 10 the description field will exceed the 16 value.
The description field need to be
Public bug reported:
It has been brought to my attention by a user the following :
Pacemaker fails to start if its PID is greater than 9, then it
reports a Library error as follow :
notice: mcp_read_config: Configured corosync to accept connections from
group 124: Library error (2)"
**
A test package that can be found here [ppa:slashd/sf99715] including the
upstream commit [0766a3ca5473a9e126e91022075b4b3798b8d5bc] has been
tested by a user affected by this issue.
Here's the user feedbacks :
"Patched version does seem to fix the issue."
Eric
--
You received this bug
** Changed in: openldap (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593378
Title:
crash in slap_bv2ad using repeated t
In frame #1
(gdb) p tags
$2 = {{bv_len = 7,
bv_val = 0x7f672c104866
"lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;lang-de;lang-encn;la"...},
{bv_len = 9,
** Changed in: openldap (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Tags added: sts
** Changed in: openldap (Ubuntu Trusty)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
(Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: libqb (Ubuntu Wily)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: libqb (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: libqb (Ubuntu Wily)
Importance:
Trusty and Wily are affected :
#define CONNECTION_DESCRIPTION (16)
Xenial is not affected :
#define CONNECTION_DESCRIPTION (34) /* INT_MAX length + 3 */
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: libqb (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595627
Title:
Pacemaker fails to start and reports a Library Error
To manage
** Patch removed: "xenial_libpam-sshauth_0.3.1-1ubuntu1"
https://bugs.launchpad.net/ubuntu/trusty/+source/libpam-sshauth/+bug/1507798/+attachment/4524268/+files/lp1507798_xenial_0.3.1-1ubuntu1.debdiff
** Patch removed: "trusty_libpam-sshauth_0.3.1-2"
Here's a new version of my patch for "Trusty" without #define
SSH_AUTH_METHOD_PUBLICKEY in auth_funcs.c and rely on the version in
pam_sshauth.h)
** Patch added: "trusty_0.3.1-2.debdiff"
Here's a new version of my patch for "Xenial" without #define
SSH_AUTH_METHOD_PUBLICKEY in auth_funcs.c and rely on the version in
pam_sshauth.h)
** Patch added: "xenial_0.3.1-1ubuntu1.debdiff"
To continue my previous comment...
It is reproducible with :
binfmt-support (2.1.6-1)
systemd(229-4ubuntu6)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1555760
Title:
Too many levels
I don't have the error "Too many levels of symbolic links" when doing an
"ls" command but I do have a problem using "df" on Xenial after
installing Openstack with lxd using "conjure-up"
"df" works fine, but after a reboot, it hangs.
A "strace df" shows that it hangs at doing :
..
It has been brought to my attention by a user experiencing the issue on
Trusty (14.04 LTS) the following :
"I installed libqb0 from proposed repo and it works as expected. No more
issues when starting with pid >99,999"
Eric
** Tags removed: verification-needed
** Tags added: verification-done
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Summary changed:
- kernel panic (General protection fault) on module hpsa (lockup_detected)
+ General protection fault panic on module hpsa with lockup_detected attribute
--
You received this bug notification because
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595627
Title:
Pacemaker fails to start and reports a Library Error
To manage notifications about this bug go to:
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593378
Title:
crash in slap_bv2ad using repeated tags
To manage notifications about this bug go to:
** Description changed:
[Impact]
libpam-sshauth v0.1-1 (shipped with precise) used to support publickey
authentication with ssh-agent.
New version of this lib shipped with trusty and late has dropped this
feature; which is related to upstream author (ltsp-upstream) switching
to
It has been brought to my attention ...
--
I confirm that the proposed testfix package resolved the issue on Trusty.
The test were made on test machines where the client had an iptable postrouting
nat forcing the source port to be under 123.
- ntpdate command performed on the client machine was
It has been brought to my attention ...
--
I confirm that the proposed testfix package resolved the issue on Trusty.
The test were made on test machines where the client had an iptable postrouting
nat forcing the source port to be under 123.
- ntpdate command performed on the client machine was
** Tags removed: verification-done
** Tags added: verification-done-trusty
--
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/1479652
Title:
[patch] ntpd rejects source UDP ports less than
I confirmed the package"4.2.6.p3+dfsg-1ubuntu3.9" solved the problem in
Ubuntu Precise
NTP Version : 1:4.2.6.p3+dfsg-1ubuntu3.1
With no IPTABLES rule ==> Working
$ ntpdate x.x.x.x
11 Feb 16:15:19 ntpdate[1243]: adjust time server x.x.x.x offset 0.190571 sec
With IPTABLES rule ==> Not working
$
** Tags removed: verification-done
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479652
Title:
[patch] ntpd rejects source UDP ports less than 123 as bogus
I confirmed the package"4.2.6.p3+dfsg-1ubuntu3.9" solved the problem in
Ubuntu Precise
NTP Version : 1:4.2.6.p3+dfsg-1ubuntu3.1
With no IPTABLES rule ==> Working
$ ntpdate x.x.x.x
11 Feb 16:15:19 ntpdate[1243]: adjust time server x.x.x.x offset 0.190571 sec
With IPTABLES rule ==> Not working
$
I confirmed the package "4.2.6.p5+dfsg-3ubuntu8.2" solve the bug in
Ubuntu Wily
# With port <123 using ntpdate (without patch)
11 Feb 20:30:09 ntpdate[2348]: no server suitable for synchronization found
# With port <123 using ntpdate (including patch)
11 Feb 20:32:18 ntpdate[3243]: adjust time
I confirmed the package "4.2.6.p5+dfsg-3ubuntu8.2" solve the bug in
Ubuntu Wily
# With port <123 using ntpdate (without patch)
11 Feb 20:30:09 ntpdate[2348]: no server suitable for synchronization found
# With port <123 using ntpdate (including patch)
11 Feb 20:32:18 ntpdate[3243]: adjust time
** Changed in: sosreport (Ubuntu Trusty)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449131
Title:
sosreport does not collect logs for Landscape Dedicated
It also been brought to my attention the following about the hotfix
kernel:
--
Hi Eric,
We have applied the update from your PPA to the controller nodes and
they have been stable over the weekend. We will see if they remain
stable under load over the rest of the week.
Thanks
--
Eric
--
You
** Changed in: openipmi (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/1546735
Title:
openipmi package compile without SSL
To manage notifications about
** Changed in: openipmi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1546735
Title:
openipmi package compile without SSL
To manage
Following a discussion with the Debian distribution maintenance software "Noël
Köthe ".
SSL support has been enabled by debian upstream maintainer and has now landed
in unstable in openipmi-2.0.21.
--
You received this bug notification because you are a member of Ubuntu
Server
Following a discussion with the Debian distribution maintenance software "Noël
Köthe ".
SSL support has been enabled by debian upstream maintainer and has now landed
in unstable in openipmi-2.0.21.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Debian package for unstable
# filename: openipmi-2.0.21/debian/changelog
openipmi (2.0.21-1) unstable; urgency=medium
...
* enabled openssl. closes: #775847
...
-- Noël Köthe Thu, 25 Feb 2016 12:06:21 +0100
--
You received this bug notification because you are a member
Debian package for unstable
# filename: openipmi-2.0.21/debian/changelog
openipmi (2.0.21-1) unstable; urgency=medium
...
* enabled openssl. closes: #775847
...
-- Noël Köthe Thu, 25 Feb 2016 12:06:21 +0100
--
You received this bug notification because you are a member
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546320
Title:
crash starting at kernel v3.13.0-72 in timer code
Rectification about the hotfix instruction procedure on comment #11.
Instructions
--
# Add the PPA to your system
$ sudo add-apt-repository ppa:slashd/bug1546320-hotfix
# Resynchronize the package index files from their sources
$ sudo apt-get update
# Installing the packages desired for
** Changed in: ntp (Ubuntu Precise)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: ntp (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: ntp (Ubuntu Wily)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed i
** Changed in: ntp (Ubuntu Precise)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: ntp (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: ntp (Ubuntu Wily)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed i
** Description changed:
[Impact]
If an NTP client sends a request with a source port less than 123, the
packet is silently ignored by ntpd. This is occurring in our environment
due to NAT.
[Test Case]
The problem can easily be reproduced by having an iptable postrouting
nat
** Description changed:
[Impact]
If an NTP client sends a request with a source port less than 123, the
packet is silently ignored by ntpd. This is occurring in our environment
due to NAT.
[Test Case]
The problem can easily be reproduced by having an iptable postrouting
nat
** Description changed:
[Impact]
If an NTP client sends a request with a source port less than 123, the
packet is silently ignored by ntpd. This is occurring in our environment
due to NAT.
[Test Case]
The problem can easily be reproduced by having an iptable postrouting
nat
** Description changed:
[Impact]
If an NTP client sends a request with a source port less than 123, the
packet is silently ignored by ntpd. This is occurring in our environment
due to NAT.
[Test Case]
The problem can easily be reproduced by having an iptable postrouting
nat
I have build a test package for the community to validate it solve the bug
before starting the SRU process [1].
The goal of this testfix is only to confirm that this solve the bug and it is
not a final solution.
Here's what has been brought to my attention about the test package I
have
I have build a test package for the community to validate it solve the bug
before starting the SRU process [1].
The goal of this testfix is only to confirm that this solve the bug and it is
not a final solution.
Here's what has been brought to my attention about the test package I
have
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479652
Title:
[patch] ntpd rejects source UDP ports less than 123 as bogus
To manage notifications about this bug go to:
** Tags added: sts
--
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/1479652
Title:
[patch] ntpd rejects source UDP ports less than 123 as bogus
To manage notifications about this bug go
** Description changed:
+ [Impact]
+
+ If an NTP client sends a request with a source port less than 123, the packet
is silently ignored by ntpd.
+ This is occurring in our environment due to NAT.
+
+ [Test Case]
+
+ The problem can easily be reproduced by having an iptable postrouting
+ nat
** Description changed:
+ [Impact]
+
+ If an NTP client sends a request with a source port less than 123, the packet
is silently ignored by ntpd.
+ This is occurring in our environment due to NAT.
+
+ [Test Case]
+
+ The problem can easily be reproduced by having an iptable postrouting
+ nat
Patch
--
Distribution : Trusty (14.04)
Package version : ntp_4.2.6.p5+dfsg-3ubuntu2.14.04.8
--
Note: kick-d is currently working on a merge for Xenial, including this patch.
I'm including the .debdiffs for the other distributions (W/T/P) for once the
merge for Xenial will be completed.
**
Patch
--
Distribution : Trusty (14.04)
Package version : ntp_4.2.6.p5+dfsg-3ubuntu2.14.04.8
--
Note: kick-d is currently working on a merge for Xenial, including this patch.
I'm including the .debdiffs for the other distributions (W/T/P) for once the
merge for Xenial will be completed.
**
Patch
--
Distribution : Precise (12.04)
Package version : 4.2.6.p3+dfsg-1ubuntu3.9
--
** Patch added: "precise_ntp_4.2.6.p3+dfsg-1ubuntu3.9"
https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1479652/+attachment/4556380/+files/lp1479652_precise_3.9.debdiff
--
You received this bug
Patch
--
Distribution : Precise (12.04)
Package version : 4.2.6.p3+dfsg-1ubuntu3.9
--
** Patch added: "precise_ntp_4.2.6.p3+dfsg-1ubuntu3.9"
https://bugs.launchpad.net/ubuntu/precise/+source/ntp/+bug/1479652/+attachment/4556380/+files/lp1479652_precise_3.9.debdiff
--
You received this bug
101 - 200 of 3441 matches
Mail list logo