00:49.34 | *** join/#wowace Megalon (~wig0r@213-157-158-146.adsl.highway.telekom.at) |
01:20.36 | *** join/#wowace purl (ibot@rikers.org) |
01:20.36 | *** topic/#wowace is https://wowace.com/ | 7.3.x ToC: 70300 | https://wowace.com/paste/ | http://lua.org | This channel is logged, via purl |
02:21.05 | *** join/#wowace Seerah (~umsin@2601:3c2:101:320:64f9:56d6:4219:6d7f) |
03:02.51 | *** part/#wowace Seerah (~umsin@2601:3c2:101:320:64f9:56d6:4219:6d7f) |
05:48.30 | *** join/#wowace ShadniX (dagger@p4FF9F00F.dip0.t-ipconnect.de) |
09:26.15 | *** join/#wowace Megalon (~wig0r@213-157-153-43.adsl.highway.telekom.at) |
09:49.27 | *** join/#wowace Kesava (~kesava@unaffiliated/sliker) |
09:51.31 | *** join/#wowace ls- (~ls@183.88.0.209) |
12:49.47 | *** join/#wowace stolenlegacy (~stolenleg@unaffiliated/stolenlegacy) |
14:05.54 | znf | https://www.reddit.com/r/Shoplifting/ |
14:05.55 | znf | the fuck |
14:07.25 | quiescens | go to sleep znf |
14:07.35 | znf | screw you, cookie monster, I just woke up! |
14:07.42 | quiescens | o.o |
14:08.48 | Torhal | lifts znf's car. |
14:09.11 | znf | ha, this is news |
14:09.17 | znf | amazon sells anti-rfid fabric |
14:09.28 | znf | these fuckers are lining up their purses/jackets/bags with them |
14:17.55 | Fisker | hey Torhal |
14:17.56 | Fisker | come here |
14:18.45 | Torhal | Can't, Fisker - znf will steal me stuff. |
14:19.51 | Fisker | :( |
14:24.49 | znf | https://www.reddit.com/r/Whatcouldgowrong/comments/7po1ic/when_i_dont_plan_the_theft_well/?st=JCBTM7PY&sh=a584d1bd |
14:24.53 | znf | hahahaha |
14:38.54 | Fisker | using the gun was really stupid |
14:43.49 | Funkeh` | faulty microcode, well done intel |
14:44.05 | quiescens | what did they do? |
14:44.52 | Funkeh` | getting bios updates pulled because bad |
14:46.27 | znf | jesus |
15:16.36 | *** join/#wowace ls-_ (~ls@223.204.246.151) |
15:18.26 | *** join/#wowace Elmoe_ (~Elmoe@24.18.143.238) |
15:18.26 | *** join/#wowace vince` (vschiu@50.35.70.27) |
15:47.48 | znf | so, just having explorer.exe opened slows down my UI to a crawl |
15:47.52 | znf | either explorer.exe or taskmanager |
15:47.56 | znf | fucking hell windows 10 |
15:48.03 | quiescens | grats |
15:48.49 | Stanzilla | yeah |
15:48.53 | Stanzilla | thank intel |
15:49.21 | Stanzilla | happens all the time here |
15:50.02 | znf | intel? I still have that shit turned on |
15:50.06 | znf | haven't patched spectre crap |
15:50.38 | quiescens | you didn't patch anything? |
15:50.48 | znf | only 1 server |
15:51.02 | quiescens | nothing with auto updates? |
15:51.29 | Stanzilla | my pc is super broken since the spectr/meltdown patches |
15:51.53 | znf | quiescens, you need to reboot that! |
15:51.55 | znf | for |
15:52.30 | quiescens | reboots znf |
15:53.13 | Funkeh` | Stanzilla: did you update bios |
15:53.22 | Stanzilla | Funkeh`: there are no updates for my bios |
15:54.19 | znf | with all the broken shit out there |
15:54.22 | znf | I'm really afraid to patch servers now |
15:54.34 | quiescens | i expect the majority of motherboards won't have updates |
15:55.24 | Stanzilla | same |
15:55.39 | quiescens | most people will make do with the OS level updates |
15:56.06 | quiescens | for one thing, bios updates mostly won't happen because it most often isn't automated |
15:56.49 | znf | I think the whole exploit thing is a bit over-exagerated |
15:57.15 | znf | I mean, sure, it's very bad, but it's kind of hard to actually exploit random machines |
15:57.17 | quiescens | i feel like we had this line of discussion when we had the last microcode update |
15:57.55 | quiescens | (in reference to the most people not getting or even having available bios updates) |
16:03.32 | Funkeh` | it's over-exagarated because the main vector for exploits tend to be the web, and chrome is already isolated from the problem |
16:04.08 | quiescens | what did chrome do? |
16:05.50 | znf | isolate! |
16:06.51 | Funkeh` | oh i'm wrolng it's not until chrome 64 in a week or 2 |
16:06.59 | Funkeh` | but you can already enable it yourself |
16:07.15 | quiescens | what did they supposedly do? |
16:07.31 | Funkeh` | https://support.google.com/faqs/answer/7622138 |
16:08.03 | znf | ah, I'm on 65 |
16:08.22 | Funkeh` | i've already enabled site isolation, is it on by default in 65? |
16:08.55 | znf | hmm, nope |
16:09.10 | Funkeh` | then they must be talking about other mitigations |
16:10.39 | Funkeh` | i wonder what problems they are grappling with that's stopping them enabling it by default yet |
16:10.49 | quiescens | site isolation doesn't really make it safe |
16:10.55 | Funkeh` | probably the usual bitching from people of "too much ram" and too many processes" |
16:11.16 | Funkeh` | it explicitly states it does |
16:11.40 | quiescens | it wasn't intended to be enabled by default when originally developed |
16:11.58 | quiescens | no it doesn't |
16:12.04 | quiescens | it says it provides mitigation |
16:12.28 | Funkeh` | what does "provides mitigation" mean to you exactly? |
16:12.52 | quiescens | not the same as being immune |
16:13.13 | Funkeh` | they would never say being immune to anything... |
16:13.18 | quiescens | the performance.now() adjustments that browsers implemented are also classed as "mitigation" |
16:13.25 | Funkeh` | another variant may crop up that exploits it in a different manner |
16:14.02 | Funkeh` | yes, because it mitigates against the currently demoed version of the JS exploit |
16:18.34 | Funkeh` | https://www.chromium.org/Home/chromium-security/site-isolation |
16:18.41 | Funkeh` | "We are working to resolve these issues so that Site Isolation can be enabled more broadly." |
16:18.57 | Funkeh` | seems to me they do intent to enable it, just not yet |
16:19.58 | Funkeh` | the main issues, as expected "Higher memory use (about 10-20% when isolating all sites with many tabs open)" |
16:22.30 | quiescens | sorry, i didn't mean it isn't ever going to be default, just that it wasn't developed for this specifically and probably won't be on by default within the timeframe of this particular vulnerability |
16:22.35 | quiescens | ): |
16:23.06 | quiescens | they are going to put other mitigations in place by default, but probably not that one |
16:23.49 | *** join/#wowace Megalon (~wig0r@213-157-153-43.adsl.highway.telekom.at) |
16:25.32 | Funkeh` | indeed, and thus brings me back to my original point |
16:25.44 | Funkeh` | the main importance will be an up to date browser |
16:26.13 | Funkeh` | but well, nothing new there |
16:36.52 | znf | let's see if my AMD server boots back up |
16:38.54 | *** join/#wowace Funkeh` (~Funkeh`@WoWUIDev/WoWAce/Ace3/BigWigs/funkeh) |
16:38.54 | *** mode/#wowace [+o Funkeh`] by ChanServ |
17:10.37 | znf | https://www.reddit.com/r/bestof/comments/7qbyab/guy_knows_girl_in_gif_helped_her_start_a_career/ |
17:10.37 | znf | heh |
17:12.26 | znf | meanwhile, back in AMD land |
17:12.47 | znf | I can't make the openvswitch module compile for the new kernel on this debian install |
17:12.52 | znf | so that means either: |
17:12.59 | znf | 1) revert kernel |
17:13.01 | znf | 2) upgrade OS |
17:14.54 | Funkeh` | option 2, always option 2 |
17:15.52 | znf | yeah, no |
17:16.06 | znf | takes 2-3 hours to set up everything required for the function of this system |
17:16.31 | Funkeh` | boohoo |
17:17.26 | znf | I hate this virtualization setup so fucking much |
18:54.46 | *** join/#wowace Gethe__ (~Gethe@cpe-70-112-184-154.austin.res.rr.com) |
19:21.59 | *** join/#wowace Funkeh` (~Funkeh`@WoWUIDev/WoWAce/Ace3/BigWigs/funkeh) |
19:21.59 | *** mode/#wowace [+o Funkeh`] by ChanServ |
19:42.47 | znf | this is why you don't use shit filesystems https://i.imgur.com/Iv7wd7j.png |
20:27.04 | *** join/#wowace Funkeh` (~Funkeh`@WoWUIDev/WoWAce/Ace3/BigWigs/funkeh) |
20:27.04 | *** mode/#wowace [+o Funkeh`] by ChanServ |
21:08.55 | *** join/#wowace Seerah (~umsin@2601:3c2:101:320:64f9:56d6:4219:6d7f) |
23:42.38 | *** join/#wowace Funkeh` (~Funkeh`@WoWUIDev/WoWAce/Ace3/BigWigs/funkeh) |
23:42.38 | *** mode/#wowace [+o Funkeh`] by ChanServ |