[16:21] is there list of kernel command line options to disable security mitigation for recent cpu exploits? [16:27] kantlivelong, I think "mitigations=off" will do the job, by disabling all of them [16:28] thats 5.2+ kernel though right? [16:28] suppose i could update [16:29] It's backported to older kernels in our releases, let me check for you kantlivelong [16:29] ah [16:30] kantlivelong, for Bionic (4.15): https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/tree/Documentation/admin-guide/kernel-parameters.txt#n2452 [16:30] ah cool [16:30] thats what i was lookin for [16:30] This file explain the fine tunnings to the mitigations, like to disable a mitigation for a single issue (Spectre only for example) [16:31] Great =) [16:31] This is on Disco (5.0): https://kernel.ubuntu.com/git/ubuntu/ubuntu-disco.git/tree/Documentation/admin-guide/kernel-parameters.txt#n2567 [16:31] SAme thing basically heheh [16:31] You may be using 5.0 as Bionic HWE for example [16:32] gonna give this a shot [16:32] cool, hope it helps you [16:32] only real concern is js but think firefox mitigated that [16:33] Hmm..not sure about that. The advise is usually to keep mitigations enabled, although I can see how it may affect some workloads' performance heheh [16:33] otherwise its all trusted code running [16:33] It's a per-case decision I guess [16:33] desktop gaming/dev pc [16:33] older [16:34] tyty [16:35] yw =) [16:42] maybe don't do banking on it [16:42] or similar [16:43] or just close ff and open w/ bank alone [16:43] and development might depend on what sort; if it's all open source there are probably easier ways to "steal" your code, like using git... ;) [16:43] no real concern other than ff [16:46] kantlivelong: firefox reduced their timer precision which makes it more difficult to carry out speculative attacks using JS [16:46] which means an attack would probably take a lot longer [16:48] https://www.mozilla.org/en-US/security/advisories/mfsa2018-01/ [16:48] they call it a partial, short-term mitigation (which is a fair description) [16:48] I don't know if they've done anything in addition to that initial change [16:49] probably not much else they can do without removing functionality === mamarley_ is now known as mamarley === joedborg_ is now known as joedborg === vaishali_ is now known as vaishali === kantlive- is now known as kantlivelong === kloeri_ is now known as kloeri [22:16] for some reason the verbose boot text, desktop, picture on the screen is "more grey" (dunno how to put it) wheen booting kernel 5.3 vs 4.15 [22:16] no such issue in 5.0 [22:16] in short, my displays look at lot cheaper when booting 5.3 :) [22:17] displays connected by displayport, intel skylake graphics [22:17] imagine looking at a cheap-ass LCD vs a decent one at best buy. one has excellent black, the other will be tainted by a grey hue [22:21] booting debian testing kernel 5.3=no issue [22:22] ubuntu 18.04-hwe-edge was affected both before and after todys update