1208
submitted 7 months ago by possiblylinux127@lemmy.zip to c/linux@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] Aatube@kbin.melroy.org 238 points 7 months ago

Don't forget all of this was discovered because ssh was running 0.5 seconds slower

[-] Steamymoomilk@sh.itjust.works 91 points 7 months ago

Its toooo much bloat. There must be malware XD linux users at there peak!

[-] rho50@lemmy.nz 95 points 7 months ago* (last edited 6 months ago)

Tbf 500ms latency on - IIRC - a loopback network connection in a test environment is a lot. It's not hugely surprising that a curious engineer dug into that.

[-] ryannathans@aussie.zone 40 points 7 months ago

Especially that it only took 300ms before and 800ms after

[-] Jolteon@lemmy.zip 80 points 7 months ago

Half a second is a really, really long time.

[-] lurch@sh.itjust.works 26 points 7 months ago

reminds of Data after the Borg Queen incident

[-] Olgratin_Magmatoe@lemmy.world 2 points 7 months ago

Which ep/movie are you referring to?

The one where they go back in time but the whales were already nuked

[-] luthis@lemmy.nz 1 points 7 months ago

I... actually can't tell if you're taking the piss or if that's a real episode.

I have so many questions about the whales.

[-] lurch@sh.itjust.works 3 points 7 months ago

Star Trek: First Contact

[-] Olgratin_Magmatoe@lemmy.world 6 points 7 months ago

If this exploit was more performant, I wonder how much longer it would have taken to get noticed.

[-] imsodin@infosec.pub 52 points 7 months ago

Technically that wasn't the initial entrypoint, paraphrasing from https://mastodon.social/@AndresFreundTec/112180406142695845 :

It started with ssh using unreasonably much cpu which interfered with benchmarks. Then profiling showed that cpu time being spent in lzma, without being attributable to anything. And he remembered earlier valgrind issues. These valgrind issues only came up because he set some build flag he doesn't even remember anymore why it is set. On top he ran all of this on debian unstable to catch (unrelated) issues early. Any of these factors missing, he wouldn't have caught it. All of this is so nuts.

[-] oce@jlai.lu 34 points 7 months ago

Is that from the Microsoft engineer or did he start from this observation?

[-] whereisk@lemmy.world 45 points 7 months ago

From what I read it was this observation that led him to investigate the cause. But this is the first time I read that he's employed by Microsoft.

[-] Quill7513@slrpnk.net 15 points 7 months ago

I've seen that claim a couple of places and would like a source. It very well may be since Microsoft prefers Debian based systems for WSL and for azure, but its not something I would have assumed by default

[-] dan@upvote.au 6 points 7 months ago

AFAIK he works on the Azure PostgreSQL product.

[-] Aatube@kbin.melroy.org 4 points 7 months ago

His LinkedIn, his Twitter, his Mastodon, and the Verge, for starters.

[-] itsnotits@lemmy.world 4 points 7 months ago

but it's* not something

this post was submitted on 01 Apr 2024
1208 points (99.2% liked)

Linux

48033 readers
948 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS