Notices by Graham Sutherland / Polynomial (gsuberland@chaos.social)

it's 5:55am and 55 seconds, on 5/5, and I'm wishing a happy 55th birthday to the 555 timer.

@SuperDicq @lily you and I are, sure. but someone has to have a business model to make RISC-V SoCs suitable for general purpose computing, and the ecosystems around them.

@lily @SuperDicq and if they roll their own RISC-V SoC ASIC to appeal to that philosophy then the price is only gonna go up.

@lily @SuperDicq I'm on the fence with this. on the one hand a very good RISC-V implementation has the potential to be quite lucrative in the cloud hosting market, since it's a good choice for horizontally scaling small low power instances - small die size per core, low quiescent power consumption, decently mature compiler support, plenty of groundwork laid by the embedded systems industry. on the other hand it has to compete with ARM, which has a headstart in a bunch of different ways.

@SuperDicq @lily IP licensing costs are basically the only market pressure I can think of that might drive people that way, but whether or not that's sufficient is a much harder question to answer.

@RikerGoogling what d'you think the B stands for

@ryanc and that's if you only count the internal registers for the main x86-64 cores and the surrounding cache/memory architecture.

if we include internal registers for UPI, PCIe, integrated graphics, TPM, IOMMU, VT-d/VT-x, and features like AMT and VROC, there's thousands of them.

@steter and if they REALLY wanted to freak us out, they'd turn them 180° so they showed back up in orbit.

"immune to cosmic radiation" is a bold claim and one I think we should test by putting them in the path of a gamma ray burst

@whitequark @timonsku really braindead tip: search "ultrasonic kinfe" or "ultrasonic knjfe", because AliExpress censors the word "knife" in listings 🙃

@whitequark @tef and I am fairly confident that a large part of the 1-2 year spike will primarily be driven by simple renewed interest in fuzzers, rather than the actual capabilities of an LLM integration.

@whitequark @tef the main thing they seem to be novel at is guiding based on semantics on top of the traditional deterministic analysis methods. which is very neat, but yeah, as you say, not world changing.

@whitequark @tef also be extremely suspicious of anyone who references any article that's like "here are hundreds of REAL VULNERABILITIES identified by an LLM!" because not a single one of those I've looked at has had anything close to 10% of them be real actual security bugs, and most of the rest are low/info stuff you could've found with a linter.

this doesn't just come up in domain name whitelisting, it's eeeeverrryyywhere. the double escapes ALWAYS catch people out. use the regex literals, they'll save your ass. and if your language or toolchain or linter has a strict mode that can yell at you about bogus escape sequences in strings (or in regex literals too, for that matter) then turn it on and turn it up to 11.

imo languages should default to making invalid string escape sequences a compile error. so please go yell at (by which I mean "politely but firmly ask") your neighbourhood language standards committee to be strict on this. by default. so I don't keep finding this bug class for another 15 years.

protip: ALWAYS use regular expression literals in JavaScript and TypeScript and any other language that supports it, instead of writing your regex out in a string. I cannot count how many critical security bugs I have found over the years from someone writing a regex like "^en\.wikipedia\.org$", which is incorrect because the \. is treated as *string* escape sequence (an invalid one that just produces .) which then results in the regex being "^en.wikipedia.org$" which matches "enowikipedia.org".

@thomasfuchs if a reboot isn't fixing it but a power-off is, then that's either a hardware or firmware issue on the NIC.

@jessew 100% someone intended to steal it and then snuck it back into the truck when they realised it was being investigated

speaking of which it looks like they got a radio glitch on the telemetry, a single sample lost to 5s of radio lock loss (0.1Hz transmit period). they're on a hold to investigate but have concluded that it's not a violation.

checks complete, radio lock restored, no constraints, hold cleared, everyone reports go for T-10m to launch!