1515377166 Q * guerby Remote host closed the connection
1515377291 J * guerby ~guerby@ip165.tetaneutral.net
1515379928 J * fstd_ ~fstd@xdsl-81-173-153-150.netcologne.de
1515380380 Q * fstd Ping timeout: 480 seconds
1515380380 N * fstd_ fstd
1515397952 J * Ghislain ~ghislain@81.56.195.31
1515399454 M * Ghislain seems 4.1 will not be updated soon for meltdown and other, do you reverted to older kernels ?
1515399507 Q * dustinm` Quit: Leaving
1515399543 M * Ghislain anyone running with the latest 3.2 right now ?
1515399565 J * dustinm` ~dustinm`@68.ip-149-56-14.net
1515399758 M * Guy- I'm not _that_ worried about meltdown and spectre, so no
1515400408 M * gnarface no chance for 4.9 ?
1515400413 M * Ghislain you run 4.1 ?
1515400436 M * gnarface i'm using 4.1 yea
1515400439 M * Ghislain 4.14 is on the work but i think Bertl is no yet there
1515400441 M * gnarface not running javascript on it though
1515400458 M * Ghislain any code run on the machine can read the memory including kernel one
1515400469 M * Ghislain that means any guest can read the memory of all others
1515400530 M * Ghislain so im am a little worried as some guest run CMS and we all know how secure those are
1515400595 M * gnarface cms?
1515400629 M * Ghislain wordpress joomla prestashop etc..
1515400638 M * gnarface ah yea, none of that either
1515400661 M * gnarface but you're right, it's a risk
1515400678 M * gnarface but let's face it, i think most of the exploits are gonna be javascript based...
1515400817 M * Ghislain yes but that stills bothers me :(
1515400933 J * nikolay ~nikolay@149.235.255.3
1515400955 M * gnarface i wonder if there would be a way to detect that some code was actively trying the exploit
1515401030 M * Ghislain seems unlikely from what i seeen on the articles i read
1515403035 J * Evannely ~Evannely@8L3AAAT7K.tor-irc.dnsbl.oftc.net
1515403069 Q * Evannely Quit: Leaving.
1515403763 Q * PowerKe Read error: Connection reset by peer
1515408759 Q * Aiken Remote host closed the connection
1515408895 J * Aiken ~Aiken@2001:44b8:2168:1000:b26e:bfff:fe2a:b951
1515410087 M * Ghislain just tried to compile 
1515410100 M * Ghislain 3.2.98 but got a reject: Hunk #1 FAILED at 69. 
1515410100 M * Ghislain 1 out of 1 hunk FAILED -- saving rejects to file init/main.c.rej
1515414112 Q * Aiken Remote host closed the connection
1515418968 M * Jb_boin so there are no meltdown/spectre patched vserver kernel so far, right?
1515420349 M * Guy- no official ones, no
1515420652 M * Ghislain i know that 4.1 is not patched and 3.2 has a reject , not tested the others
1515424136 M * Ghislain oh 3.18 just popped up
1515424450 M * Ghislain well we all know this is the nsa that introduced this bug like they done it for RSA ;p
1515426130 J * Le_Coyote ~smokey@253.242.118.78.rev.sfr.net
1515426138 M * Le_Coyote Hullo again
1515426208 M * Le_Coyote What's the status of vserver-able kernels regarding meltdown and spectre?
1515426223 M * Le_Coyote Is 3.18 patched? 4.1? What should we expect? Chhers :)
1515426257 M * Le_Coyote daniel_hozac: btw, any thoughts about removing/changing the __constructor__ declarations in vserver-stat.c so that it can be built with SSP?
1515426354 M * Ghislain 4.1 is not patched by mainline so it cannot be in vserver
1515426419 M * Ghislain it seeems that under 4.4 mainline did not have a solution, i dont see anything in the changelog about 3.18 and others
1515426452 M * Ghislain 3.2 seems to have a backport of kaiser
1515426530 M * Le_Coyote So … the bottomline is there are no vserver kernels with available fixes?
1515426545 M * Le_Coyote Except for 3.2 ?
1515426563 M * Ghislain so for mainline 3.2, 4.4 4.9 and 4.14 seems  to have the patchs. On those 4 3.2 have patch for vserver but the patch released yesterday have a reject for the 3.2 of today
1515426568 M * Ghislain yes
1515426593 M * Le_Coyote So I'd have to downgrade. Igh.
1515426595 M * Le_Coyote Ugh*
1515426672 M * Le_Coyote Let's wait for a while and see what happens then
1515426687 M * Ghislain well its not a kernel bug, this is a hardware bug that necessitate a change in the way the kernel work so it do not trust anymore the cpu on some informations
1515426688 M * Le_Coyote I'd hate to move to KVM but I'm considering it more and more :S
1515426707 M * Le_Coyote Oh I do understand the magnitude of the issue
1515426727 M * Ghislain re engennering the kernel is not easy nor fast. The BSD have none, linux mainline have just a few
1515426740 M * Ghislain and this is not fixing spectre, only meltdown
1515426780 M * Ghislain second issue: rushed reengeneered kernel smell stability and perf and security issues to come
1515426788 M * Le_Coyote True.
1515426799 M * Ghislain so i bet we will have waves of kernel patche for several month
1515426818 M * Ghislain and Bertl will probably have his brain melt by the load :p
1515426824 M * Le_Coyote I'll bet :)
1515426852 M * Ghislain perhaps he will have to watercool the brain
1515426900 M * Le_Coyote Odd how 4.1 hasn't received any attention yet, regarding those two bugs
1515426958 M * Le_Coyote Then again, I guess downgrading from 3.18 to 3.2 wouldn't be such a huge problem
1515427119 M * Ghislain well 4.1 to 4.4 has major changes in the kernel. That means backporting is not easy
1515427137 M * Ghislain but 3.2 having kaiser is strange
1515427381 M * Le_Coyote "Indeed".
1515429139 Q * Jb_boin Remote host closed the connection
1515429469 Q * nikolay Quit: Leaving
1515429760 J * Jb_boin ~dedior@proxad.eu
1515431827 M * daniel_hozac Le_Coyote: have you figured out why SSP fails with them?
1515434845 M * Le_Coyote daniel_hozac: nope, that's beyond my skills, but my googling suggests it's got to do with inlining by the pre-compiler, if that makes any sense?
1515436521 M * daniel_hozac have you run gdb to get a look at the assembly it's bailing out on?
1515439511 M * Le_Coyote daniel_hozac: nope, only went as far as to see that it was because of these two functions. I don't even know how to check the assembly
1515440225 J * Aiken ~Aiken@2001:44b8:2168:1000:b26e:bfff:fe2a:b951
1515442190 M * arekm kvm and meltdown is also "fun" -> https://groups.google.com/forum/m/#!topic/mechanical-sympathy/L9mHTbeQLNU
1515446365 N * Bertl_zZ Bertl_oO
1515452329 Q * LongyanG Read error: Connection reset by peer
1515452634 J * LongyanG ~long@15255.s.t4vps.eu