On 05/22/2014 01:24 AM, Robie Basak wrote:
> This will probably want the attention of the kernel team for a reply, so
> forwarding there. Is there maybe a security reason why it is arranged
> this way? I note that System.map is the same.
>
It was done deliberately to make it harder for an attacke
On 04/29/2015 07:55 PM, Marc Deslauriers wrote:
> On 2015-04-29 10:44 PM, John Moser wrote:
>>
>>
>> On 04/29/2015 10:36 PM, Marc Deslauriers wrote:
>>> On 2015-04-29 12:42 AM, John Moser wrote:
On 04/29/2015 12:40 AM, Martinx - ジェームズ wrote:
>
> I am very happy with window co
On 07/30/2015 11:49 AM, christopher.carl...@zodiacaerospace.com wrote:
> Thank you for your reply, Paul.
>
> BTW, I'm running 14.04.2 LTS.x86_64.
>
> I also don't always restart, but I presume the only reason we got a kernel
> update is because of a bug or security, which encourages me to restar
On 04/06/2016 02:32 PM, Dimitri John Ledkov wrote:
> On 6 April 2016 at 22:25, Xen wrote:
>> Bryan Quigley schreef op 06-04-16 22:35:
>>> Hi all,
>>>
>>> The naming scheme of just "Ubuntu 14.04.4 LTS" is no longer
>>> meaningful when it comes to determining what kernel/mesa/xorg you are
>>> on.
On 06/23/2017 12:52 PM, Nrbrtx wrote:
> Dear Ubuntu developers!
>
> I can't understand how this happen, but your latest kernel upgrade broke many
> user-space applications.
>
> For me this process was started from Scilab. I can't use it with new kernels
> (linux-image-3.13.0-121-generic on 14.0
On 10/11/2017 07:20 AM, Thomas Gertin wrote:
> Thanks guys,
>
> Here are my CVE identifiers:
>
> CVE-2016-9843
>
> CVE-2016-9842
>
> CVE-2016-9841
>
> CVE-2016-9840
>
> I looked them up on the Ubuntu CVE tracker
> (https://people.canonical.com/~ubuntu-security/cve/)
>
> I am having trouble r
