This just in, licorice kills dogs. Once in a while it kills people too. (affects insulin production, and aldosterone causing blood pressure effects then downstream effects on blood potassium and kidneys)
It's an audio processing chip, so probably not going to show up in a charging cable. Although the engineering part of my brain says "noise" shows up in a lot of places...
"Of course it's a coincidence" doesn't leave me with good feels. See, we don't know what a "normal distribution" is for a correlation like this, it's not like we have a huge bag of samples to determine the variance from.
I wasn't thinking specifically of the speed of light, what other "significant" numbers are there and what "significant" physical artifacts correspond to them? I would expect the definition of "significant" is going to play a big part in it. In the back of my mind, some things I'm observing in how people explain what AI does make me feel like they're relying on normal distributions to carry a lot of water. If something is an "outlier / coincidence": is it? What distribution(s) does it belong to? Just a nagging feeling at this point.
Architecture Astronaut! TCP is a stream protocol. A terminal program is expected to honor the stream protocol: I can use a terminal program to speak SMTP or HTTP. I can paste binary shit into it and copy binary shit out of it (some caveats apply).
If you're gonna jack some control protocol into a session which is sitting directly on the stream protocol, that's on you. This is as airtight as injecting a control protocol into SMTP or HTTP. Encapsulate the entire protocol (obviously this requires presence on both ends), open a second channel (same), or go home. It's worth noting that the "protocol" drops a helper script on the other side; so theoretically it is possible for them to achieve encapsulation, but doing it properly might require additional permissions / access.
Obviously they published a fix, since that's how the exploit was reverse engineered. This is "...what happens when terminal output is able to impersonate one side of that feature's protocol."
Which has nothing to do with terminals, because nobody runs terminals directly over TCP. Telnet wasn’t simply sending terminal bytes over TCP, it has its own complex system of escape sequences and protocol negotiation (IAC WILL/WONT/DO/DONT/SB/SE, numerous Telnet options). SSH is even further from raw TCP than Telnet was
And a Unix pty isn’t a simple stream either. Consider SIGWINCH
Amtrak sucks in so many ways, but that said for almost a decade prior to COVID when I had the opportunity (roughly yearly) I'd travel Amtrak first class between Tacoma WA and Oakland CA (Starlight). Kind of a day's vacation going each way (and they'd sell you a tax free bottle of good wine you could wander around first class with).
It was weird, I would arrive in Oak / SF rested, grounded, not nearly as stressed... and without a flying horror story to share (although the "alien abduction" made a good story). [0]
At the end of the journey Amtrak sucked, but flying sucks more; so much of the suck is fixable in both cases but it never seems to happen.
[0] I'd rate your chances as about 1:3 something unexpected will occur. An 11PM electrical fire / "alien abduction". They put the train together wrong / in a hurry and first class was right behind the engines (they sealed the door with duct tape to keep the rain / snow / wind out), and at night going through the Cascades in OR there were a half dozen of us crowding around with our wine bottles looking out over the engines; very cool. A freight broke apart in the Cascades stretch and we sat in the bar car (drinking wine) and watched the maintenance crews humping connector knuckles from behind us up to the freight in front of us (some of those freights are over a mile long; did I mention we were basically on the side of a cliff?).
reply