01:06:16 uugh.. who thought it was good idea to propagate the whole non-NUL terminated, space padded to fixed length strings 01:06:19 this isn't the 80s 01:06:24 (KCF) 01:13:47 I wonder if AMD chips will get some update soo too: https://cachewarpattack.com/ 01:16:54 there is a microcode patch for AMD, but it only matters if your host is running a hypervisor that uses SEV 01:17:19 far smaller set of affected systems than intel's bug 13:57:48 oh it would have been nice had the kcf ARC materials had made it out the door... 13:58:40 for some reason, the system attaches, detaches, then attaches again this driver.. which shouldn't be a problem 13:59:04 except desipte crypto_register_provider()/crypto_unregister_provider() being called successfully during attach/detach 13:59:26 KCF ends up with two entries for the driver 14:00:00 (and both are in the 'ready' state.... it does appear it'll leave old ones around for a bit marked as free) 15:17:45 or rather it's supposed to do that 15:18:01 i suspect i have an upcoming date with kmdb in my future :) 15:30:49 https://lock.cmpxchg8b.com/reptar.html 15:31:03 once more bug from intel 15:31:29 CVE-2023-23583 15:37:17 Already fixed https://www.illumos.org/issues/16058 15:37:19 → BUG 16058: Update Intel microcode to 20231114 (Closed) | https://code.illumos.org/c/illumos-gate/+/3135 15:37:36 denk: see illumos#16057 15:37:58 Thanks ptribble for the link (my bad for slow typing). 15:38:32 @jbk --> kcf is beholden more than a little to the PKCS#11 standard for userland back-end. 15:39:07 thanks, I read old news :) 15:41:40 yeah, that's my guess why they decided to act like it's the 80s and they're running DOS with their non-NUL, space padded strings :P 15:41:55 though that's just a wtf 15:43:32 i've got a mostly working tpm2.0 driver, and i was going to include rng support for kcf (because we have a rather dearth of entropy sources currently) 15:44:22 and the attach / detach / attach sequence is causing a panic when you query provider info 15:45:01 because the crypto unregister doesn't appear to actually be unregistering 16:19:52 sommerfeld: hah, clever name (Runaway Reptar) 16:21:41 I imagine they can't come up with a cute logo for it given that it'd violate Nickelodeon's copyrights 19:22:32 [illumos-gate] 16049 Update AMD microcode to 20231019 -- Andy Fiddaman 21:57:27 hrm... we cap vioif's tx/rx buffer amount at 256... that does seem a bit on the low side if you're wanting to push a decent amount of data 21:57:40 probably should at least make that a dladm private property 22:20:13 am I thinking of the wrong thing, or is that one of the differences in virtio interfaces? 22:22:33 i'm not sure.. 22:24:16 i mean for comparison, a real single HW ring usually has something like 4-10x the amount 22:24:33 depending on whatever defaults the driver writer picked 22:26:28 I was thinking of the virtio queue, not this 22:26:50 (it'd be nice to add multi-queue support if the HV supports it as well) 22:29:43 jbk: I think the big difference is also the 64 KiB data size that gets allocated.