=== StoneTable is now known as aisrael
=== infinity1 is now known as infinity
=== Mirv__ is now known as Mirv
=== chiluk_ is now known as chiluk
=== acheronuk_ is now known as ackeronuk
=== blahdeblah_ is now known as blahdeblah
=== chrisccoulson_ is now known as chrisccoulson
[13:00] <TJ-> Would it be unusual for PhasedUpdate to break 'apt update'
[17:54] <wxl> should we expect CVE-2018-14665 which is now in bionic and beyond to make its way back to xenial and trusty?
[17:54] <ubottu> A flaw was found in xorg-x11-server before 1.20.3. An incorrect permission check for -modulepath and -logfile options when starting Xorg. X server allows unprivileged users with the ability to log in to the system via physical console to escalate their privileges and run arbitrary code under root privileges. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14665)
[17:55] <wxl> the patch is tiiiiny which is thankful :)
[17:56] <Faux> It's marked as unaffected: https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-14665.html
[17:56] <ubottu> A flaw was found in xorg-x11-server before 1.20.3. An incorrect permission check for -modulepath and -logfile options when starting Xorg. X server allows unprivileged users with the ability to log in to the system via physical console to escalate their privileges and run arbitrary code under root privileges. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14665)
[17:57] <wxl> oh wee
[17:57] <wxl> what's DNE?
[17:58] <Faux> Does Not Effect, or something like that. I don't know.
[17:58] <wxl> well there's also "not-affected" so i would suspect that's not another indicator for the same thing
[17:59] <wxl> ah does not exist
[17:59] <Faux> Well, I've been horribly misreading those pages.
[17:59] <wxl> which makes sensive given xorg-server-hwe-16.04 DNE's everywhere except for xenial
[18:00] <wxl> s/iv//
[18:03] <wxl> thanks Faux for pointing out the obvious for me
=== caravena_ is now known as caravena
[21:31] <rfleming> Hi.  I have a question in regards to how packages are moved from universe
[21:31] <rfleming> particularly related to https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1637988
[21:31] <ubottu> Launchpad bug 1637988 in gvfs (Ubuntu) "gvfsd-nfs not present in gvfs-backends, why?" [Wishlist,Triaged]
[21:34] <rfleming> I do understand that an inclusion requisition was asked (https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598) but how long does this process normally take?
[21:34] <ubottu> Launchpad bug 1746598 in libnfs (Ubuntu) "[MIR] libnfs" [Undecided,Confirmed]
[21:41] <jbicha> rfleming: there is a backlog for main inclusion requests. Honestly that one is not a very high priority compared to others this year
[21:42] <jbicha> btw, the Security Team is hiring: https://boards.greenhouse.io/canonical/jobs/1158266
[21:44] <rfleming> jbicha: I see.
[21:44] <rfleming> I don't know enough to be a contributor.
[21:46] <rfleming> It's missed 16.04 and 18.04... maybe it'll be ready for 20.04
=== PityDaFool is now known as AfroThundr|02
[22:25] <sarnold> rfleming: guaranteed it'll get a security review before then :) but .. I have to say I'm skeptical of the reasons for a userspace nfs implementation
[22:48] <sarnold> bdmurray:  Can't access efivars filesystem at /sys/firmware/efi/efivars, aborting --- is that really "success"?
[23:24] <bdmurray> sarnold: On a system with BIOS yeah.
[23:24] <sarnold> bdmurray: cool, thanks :)