** Patch removed: "zesty_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/zesty/+source/openssl/+bug/1674399/+attachment/4868385/+files/zesty_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
xenial_openssl_lp1674399.debdiff
** Patch added: "xenial_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/+attachment/4868386/+files/xenial_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
zesty_openssl_lp1674399.debdiff
** Patch added: "zesty_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/+attachment/4868385/+files/zesty_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch se
Here's the highligh of the discussion I had in #ubuntu-release with
infinity about my proposal in comment #6.
For SRU, I had a talk with apw and rbasak about this bug a
couples weeks ago LP: #1674399, could you please look at this bug and
based on the Descriptions and comment #6 if this looks elig
Attaching Artful debdiff
** Patch added: "artful_openssl_lp1674399.debdiff"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+attachment/4868343/+files/artful_openssl_lp1674399.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
[For SRU Verification team]
Context :
Previous IRC discussion with apw/rbasak about this case :
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2
AMD released a new CPU called "Ryzen" that now support "Intel SHA
extensions" technology.
In current Ubuntu openssl package sh
** Description changed:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
only (Confirmed with AMD representative). Current OpenSSL version in
Ryzens still calls SHA
** Description changed:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
only (Confirmed with AMD representative). Current OpenSSL version in
Ryzens still calls SHA
Another test "Openssl speed"
[Without patch]
$ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 2217067
So far my test reveal the following :
# Note that the below test has been made on a Ryzen system #
[Without patch]
* Generated a checksum of a big file (e.g. 5GB file) with openssl
$ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
SHA256(/var/tmp/5Gfile)=
8d448d81521cbc1bfdc04dd199d448bd3c
Debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861145
** Bug watch added: Debian Bug tracker #861145
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861145
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: openssl (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: openssl (Ubuntu Zesty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: openssl (Ubuntu Artful)
Assignee: (unassigned) => Eric Desrochers (slashd)
*
** Description changed:
* Context
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit
only (Confirmed with AMD representative). Current OpenSSL version in
Ryzens still calls SHA for SSSE3 routi
** Description changed:
* Context
- AMD added support in their processors for SHA Extensions[1] / CPU flag:
- sha_ni[2] starting with Ryzen CPU. Current OpenSSL version in Ryzens
- still calls SHA for SSSE3 routine as result a number of extensions were
- effectively masked on Ryzen and shows
** Description changed:
- AMD added support in their processors for SHA Extensions starting with
- Ryzen CPU. Current OpenSSL version in Ryzens still calls SHA for SSSE3
- routine as result a number of extensions were effectively masked on
- Ryzen and shows no improvement.
+ * Context
- It has
** Also affects: openssl (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu Xenial)
Status: New => Triaged
** Changed in: openssl (Ubuntu Zesty)
Status: New =
** Description changed:
+ AMD added support in their processors for SHA Extensions starting with
+ Ryzen CPU. Current OpenSSL version in Ryzens still calls SHA for SSSE3
+ routine and shows no improvement.
+
It has been brought to my attention that :
"CPUID detection in OpenSSL does not prope
** Changed in: isc-dhcp (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: isc-dhcp (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random po
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random po
** Patch removed: "lp1176046_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864920/+files/lp1176046_xenial.debdiff
** Patch added: "lp1176046_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachm
** Patch added: "lp1176046_trusty.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864919/+files/lp1176046_trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp
** Patch added: "lp1176046_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4864920/+files/lp1176046_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp
@rbasak,
* Un-version the "Replaces:" as discussed : DONE
- Upgrade Trusty->Xenial with isc-client-dhcp pkg successfully completed with
expected result
- Upgrade Trusty->Xenial with isc-client-dhcp-noddns pkg successfully completed
with expected result
* Fix typo here and there : DONE
* Add (L
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random po
** Description changed:
[Impact]
In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
The DDNS functionnality, generate 2 random extra ports between 1024-65535.
Impact reported by users :
"One impact of these random po
** Patch added: "verif-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+attachment/4864794/+files/verif-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
htt
** Patch added: "verif-trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+attachment/4864795/+files/verif-trusty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
htt
Hi Robie,
To answer your questions...
* Are you proposing your debdiff in commit 40 as ready for upload to Trusty?
No, here's the final one (that I sent you by email), but I will attach them to
the LP bug now.
verif-trusty.debdiff
verif-xenial.debdiff
* Or is it still in progress?
No, I did b
** Changed in: openssl (Ubuntu)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1674399
Title:
OpenSSL
Here's some context after a conversation about this bug on channel :
#ubuntu-release
...
[10:01:50] hi SRU, I'm currently working on a case (no LP bug yet)
about an OpenSSL bug on new AMD CPU (Ryzen) released last Feb ... where the SHA
Extension routine is not called on AMD Ryzen cores. My
* Repository : https://github.com/openssl/openssl.git
* Commits :
1aed5e1 crypto/x86*cpuid.pl: move extended feature detection.
f8418d8 crypto/x86_64cpuid.pl: move extended feature detection upwards.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Public bug reported:
It has been brought to my attention that :
"CPUID detection in OpenSSL does not properly detect potential optimizations
for AMD processors."
After further verification on my side :
Extended feature flags were not pulled on AMD processors, as result a
number of extensions we
Feedback from the field about the test package of "isc-dhcp-client-
noddns" I made for someone interested to give it a try before the SRU:
"... we've tried it out and didn’t notice anything unusual, but I
suspect we would only see problems if there are any if we ran it 1000s
of times in ci.
I als
Feedback from the field about the test package of "isc-dhcp-client-
noddns" I made for someone interested to give it a try before the SRU:
"... we've tried it out and didn’t notice anything unusual, but I
suspect we would only see problems if there are any if we ran it 1000s
of times in ci.
I als
Quick note saying that the work is still in progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
St
Great thanks Andrew !
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mec
@dwmw2,
@Andrew Jorgensen,
or anyone else affected by this bug.
As you may have notice, there is currently a call for testing a proposed
version of the source package "krb5".
This is the last step before the package make its way into xenial-
updates (final destination)
Could you please try the p
As per a irc conversation with the SRU team (apw),
The existing krb5 (1.13.2+dfsg-5ubuntu1) has a regressing ADT test so it stuck
in -proposed.
Thus, preventing krb5 (1.13.2+dfsg-5ubuntu2) to land in -proposed.
SRU team are looking at this as we speak.
- Eric
--
You received this bug notifica
** Description changed:
== SRU JUSTIFICATION ==
[Impact]
* Chrome (and other things) crash (segfault) when Kerberos fails to
authenticate.
Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdd687700 (LWP 14851)]
spnego_gss_inq
** Tags removed: sts-sponsor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mechanism failure
Status in krb5 package in Ubuntu:
Fix Released
Installing isc-dhcp-client-noddns on Trusty and then upgrade to Xenial
with a local archive of a modified Xenial's isc-dhcp-client to replace
isc-dhcp-client-noddns package to isc-dhcp-client during release upgrade
from Trusty to Xenial work as expected with a completed successful
release upgrade.
** Patch added: "V2_lp1648901_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/krb5/+bug/1648901/+attachment/4794810/+files/V2_lp1648901_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 i
** Patch removed: "V2_lp1648901_xenial"
https://bugs.launchpad.net/ubuntu/xenial/+source/krb5/+bug/1648901/+attachment/4794729/+files/V2_lp1648901_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubun
** Patch added: "V2_lp1648901_xenial"
https://bugs.launchpad.net/ubuntu/xenial/+source/krb5/+bug/1648901/+attachment/4794729/+files/V2_lp1648901_xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu
** Changed in: isc-dhcp (Ubuntu Trusty)
Importance: Medium => Wishlist
** Changed in: isc-dhcp (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.laun
DEBDIFF for Xenial [1.13.2+dfsg-5ubuntu2]
** Patch added: "lp1648901_xenial"
https://bugs.launchpad.net/ubuntu/xenial/+source/krb5/+bug/1648901/+attachment/4794021/+files/lp1648901_xenial.debdiff
** Tags added: sts sts-sponsor sts-sru
--
You received this bug notification because you are a
Here a new version of the actual in progress... debdiff for Trusty.
** Patch added: "V2_debdiff_noddns_proposal_still_in_progress"
https://bugs.launchpad.net/ubuntu/trusty/+source/isc-dhcp/+bug/1176046/+attachment/4793975/+files/V2_no_ddns_binary_pkg.debdiff
** Attachment removed: "debdiff_n
@rbasak,
Yes, right this is exactly what I had in mind.
Noted for "(no behavioural change from previous version)".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
** Description changed:
== SRU JUSTIFICATION ==
[Impact]
- Chrome (and other things) crash (segfault) when Kerberos fails to
+ * Chrome (and other things) crash (segfault) when Kerberos fails to
authenticate.
Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
** Changed in: krb5 (Ubuntu)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mechan
** Description changed:
== SRU JUSTIFICATION ==
[Impact]
Chrome (and other things) crash (segfault) when Kerberos fails to
authenticate.
Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdd687700 (LWP 14851)]
spnego_gss_inqui
Great will then start the sru on monday.
Thanks for the quick feedback.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mechanism failure
Stat
** Description changed:
== SRU JUSTIFICATION ==
[Impact]
Chrome (and other things) crash (segfault) when Kerberos fails to
authenticate.
Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdd687700 (LWP 14851)]
spnego_gss_inqui
** Changed in: krb5 (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: krb5 (Ubuntu Xenial)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: krb5 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: krb5 (Ubuntu Xenial)
St
** Description changed:
== SRU JUSTIFICATION ==
[Impact]
- Chrome (and other things) crash when Kerberos fails to authenticate:
- https://bugs.chromium.org/p/chromium/issues/detail?id=554905
+ Chrome (and other things) crash (segfault) when Kerberos fails to
+ authenticate.
Thread 2
** Description changed:
== SRU JUSTIFICATION ==
[Impact]
Chrome (and other things) crash when Kerberos fails to authenticate:
https://bugs.chromium.org/p/chromium/issues/detail?id=554905
Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thr
** Description changed:
+ == SRU JUSTIFICATION ==
+
+ [Impact]
+
+ Chrome (and other things) crash when Kerberos fails to authenticate:
+ https://bugs.chromium.org/p/chromium/issues/detail?id=554905
+
+ Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
+ [Switching to Thr
I reviewed the src code of X/Y/Z and only X is affected.
Y/Z already have the patch.
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mech
dwmw2,
Can you please give a try at this test package ?
--
$ sudo add-apt-repository ppa:slashd/fix1648901
$ sudo apt-get update
Install the necessary krb5 packages and then test your reproducer.
--
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
Ok tks that all I need for now. Will provide a test pkg on Monday for
Xenial.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mechanism failure
Dwmw2,
On which ubuntu release are you experiencing the situation ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1648901
Title:
SPNEGO crash on mechanism failure
Status i
Hi andrew, dwmw2 et al,
If I build a test package on Monday, will you be amenable to
install/test it and then provide feedbacks before I start the SRU ?
Addtionnaly, can you provide the detailed steps on how to reproduce the
problem ?
--
You received this bug notification because you are a memb
** Changed in: krb5 (Ubuntu)
Importance: Undecided => Low
** Changed in: krb5 (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: krb5 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubu
@caribou
@rbasak
Let me share the work (since rbasak seems to like the approach) I've
done so far on my above recent proposal :
isc-dhcp-client: dhclient with DDNS functionality enabled
isc-dhcp-client-noddns : dhclient with DDNS functionality disabled
This is a working debdiff, I think
Maybe we are not looking the situation the right way ... What if we look
at this the opposite way ?
"isc-dhcp-client" remains the same including the extra random bindings
ports.
and we introduce a new package "isc-dhcp-client-noddns" that change the
dhclient behavior by overriding dhclient and i
@caribou, yes you are reading this correctly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Status in isc
I will evaluate/test the "debian/control" fields possible scenarios this
week, and will update the LP with the outcome.
rbasak, if you have any ideas/suggestion/piece of advise/... I'm all
ears.
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
7.6.1 Overwriting files in other packages
It is usually an error for a package to contain files which are on the
system in another package. However, if the overwriting package declares
that it Replaces the one containing the file being overwritten, then
dpkg will replace the file from the old pack
Hmm need to look more in depth but maybe this would work ? By
mentionning the "earlier than" ootion.
* 7.3 Packages which break other packages -
Breaks normally a Breaks entry will have an "earlier than" version
clause; such a Breaks is introduced in the version of an (implicit or
explicit) depen
Rectification :
I think we will need a mix of both world Recommends: and Break: .
Need to check more in deep for implementation though (if applicable)
Recommends: for next pkg upgrade and then rely on Breaks: or something
similar to that for following pkg upgrade and release upgrade.
--
You re
> This part sounds like it'll work well then, but I'm not sure about the
change in release upgrade behaviour above.
Good point !
What about "Breaks:" instead of "Recommends:" ?
Package A breaks Package B when both packages cannot be simultaneously
configured in a system. The package management s
I picked "Recommends:" based on following explanation :
Package A recommends Package B, if the package maintainer judges that
most users would not want A without also having the functionality
provided by B.
Ref:
https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html
Eric
--
You re
> What will happen to existing Trusty users who are relying on the
current ddns functionality?
Existing Trusty user at next isc-dhcp-client pkg upgrade will
automatically receive (Recommends: isc-dhcp-client-ddns).
And for users bother by the extra random port they will simply have to
apt-get pur
** Description changed:
+ [Impact]
+
+ In trusty, there is only 1 version of dhclient, including #define NSUPDATE,
which introduce DDNS functionnality.
+ The DDNS functionnality, generate 2 random extra ports between 1024-65535.
+
+ Impact reported by users :
+
+ "One impact of these random po
-ddns : dhclient with DDNS functionality enabled (with random
extra ports)
Eric
** Changed in: isc-dhcp (Ubuntu Trusty)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: isc-dhcp (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: isc-dhcp (Ubuntu
** Changed in: isc-dhcp (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra r
** Changed in: isc-dhcp (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random por
** Tags removed: raring
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1176046
Title:
isc-dhcp dhclient listens on extra random ports
Status in isc-dhcp package in Ubunt
> But perhaps it would be simpler to provide users a way to disable this
functionality manually? Is there any kind of runtime configuration
available?
At runtime, it doesn't seem to have a way, for instance, I already tried
the following without success: do-forward-updates false;
# man dhclient.c
So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".
On Trusty, "isc-dhcp-client" combine both.
Will ask the SRU
So long story short, starting with Xenial you have the possibility to
install "isc-dhcp-client" which doesn't include the 2 extra port
bindings, but if you need it for Dynamic DNS (DDNS) you can optionally
install "isc-dhcp-client-ddns".
On Trusty, "isc-dhcp-client" combine both, and AFAIK, I don'
I was able to identify from where the port range list is initialize, and the
decision is taken by binary package "libdns162" (source package "bind9")[1]
which dhclient relies on.
Basically, it randomly takes any port available between 1024 and 65535[2]
So there is a port randomization mechanism
After more investigation, it seems like the 2 extra port-bindings port
assignation decision is made by "libdns" itself.
https://github.com/wklaebe/bind9/blob/ac1dcdd124a5abdec4969e2c33836d863bf73aa7/lib/dns/dispatch.c#L1921
--
You received this bug notification because you are a member of Ubun
Hi Richard,
Thanks for updating the bug with Dave's latest suggestion in order to
isolate this particular situation.
We will come back to you soon with the next steps.
Regards,
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
Rectification, after more investigation here what is happening :
Trusty got the random port right away because NSUPDATE is enable at
compile time in package "isc-dhcp-client"
In Xenial and late (including debian) with commit
[b1d5bab630a29f2ca94c458f9402aa43cc5975c4], a new pkg binary package is
The following debian[1] forum indicate that failover and tracing need to
be disabled in order to disable NSUPDATE as well and I confirmed the
steps, otherwise the build fails.
I'm not too sure if this is the right way to fix this problem as I don't
want to introduce new issues that will impact oth
Applying the Xenial "disable-nsupdate.patch" result in a failling build
in Trusty.
/<>/server/dhcpd.c:498: undefined reference to `trace_ddns_init'
dhcpd-failover.o: In function `dhcp_failover_process_bind_update':
/<>/server/failover.c:5225: undefined reference to `ddns_removals'
Seems like fail
NSUPDATE is disabled in Xenial, will keep the same approach for Trusty
and then test.
More details can be found here :
xenial/isc-dhcp-4.3.3/debian/patches/disable-nsupdate.patch
description: undefine NSUPDATE
author: cchip
origin: http://forums.debian.net/viewtopic.php?f=10&t=95273
bug-debian:
** Changed in: isc-dhcp (Ubuntu)
Status: Triaged => In Progress
** Changed in: isc-dhcp (Ubuntu)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-d
Then NSUPDATE has been re-enable with debian bug :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798237
# changelog
isc-dhcp (4.3.3-4) unstable; urgency=medium
* Reenable NSUPDATE (closes: #798237)
I will look at both changes, but most likely the one in #798237 seems
more suitable for a wi
Sound similar to debian bug : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=712503
The situation doesn't occur on Xenial (16.04 LTS), but present in Trusty
(14.04) as a fix has been first introduce in Ubuntu with version : isc-
dhcp (4.3.3-2)
Trusty :
#netstat -tulp | grep -i dhclient
udp
Hi scotte,
The fix is now released as shown in comment#25 & #26
Eric
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1607920
Title:
zfs services fail on firstboot if zfs
After a talk with stgraber, this is a due to the fact that the Ubuntu
LXC I build are using a pre-generated image which uses UTC by default.
If you want to change the time on Xenial, in my case date command or
other technic didn't have positive impact.
The only thing that work so far is to unlink
LXC Container has been created as follow :
$ lxc-create -t download -n trusty -- --dist ubuntu --release trusty --arch
amd64
$ lxc-create -t download -n xenial -- --dist ubuntu --release xenial --arch
amd64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Public bug reported:
With regard to github bug :
---
adjust timezone to the host at creation time #47
https://github.com/lxc/lxc/issues/47
---
I still can reproduce the problem on different HW running Xenial with
the LXC ubuntu image Trusty and Xenial.
* Bare metal (xenial)
$ date
Wed Oct 12 11
Thanks scotte for the feedbacks.
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1607920
Title:
zfs services fail on firstboot if zfs-uti
@apw
With regard to the translation
The commit has been intensively tested in different scenarios/env/...
and of course with the "ZFS Test Suite"[1] which include functionality,
perf, and stress tests.
All the tests were reported as successful.
I hope this answer your questions and address
@apw
To answer your question:
"Also as you are changing MNTTAB is there any reason not to be using that here?"
The "reading" is redirected to /proc/self/mounts and the "writing" to
/etc/mtab, but if it doesn't exist, that's fine. ZFS just won't update
/etc/mtab.
Ideally, ZFS should be integrate
As per irc conversation with apw, I'm merging both LPs #1607920 &
#1628279 into one debdiff.
** Patch added: "lp1607920_lp1628279_xenial.debdiff"
https://bugs.launchpad.net/ubuntu/xenial/+source/zfs-linux/+bug/1607920/+attachment/4753590/+files/lp1607920_lp1628279_xenial.debdiff
--
You recei
601 - 700 of 770 matches
Mail list logo
