Re:MS Paint Remote Code Execution Vulnerability
by znpy on Friday November 06, 2026 @04:30AM
(#50390164)
86-ing?
Re:MS Paint Remote Code Execution Vulnerability
by yakshaving_jgt on Friday November 06, 2026 @04:33AM
(#50390181)
It comes from working in kitchens. It means to remove something from the menu, or otherwise make it unavailable.
Re:MS Paint Remote Code Execution Vulnerability
by dboreham on Friday November 06, 2026 @08:08AM
(#50391889)
Also seashells.
Re:MS Paint Remote Code Execution Vulnerability
by SketchySeaBeast on Friday November 06, 2026 @08:24AM
(#50392009)
86 seashells? I don't even know what do with the three seashells.
Re:MS Paint Remote Code Execution Vulnerability
by zdragnar on Friday November 06, 2026 @10:05AM
(#50393204)
Surely a SketchySeaBeast could come up with uses for at least three seashells
Re:MS Paint Remote Code Execution Vulnerability
by Grimeton on Friday November 06, 2026 @11:21AM
(#50394406)
Greetings and salutations!
I understood that reference.
Re:MS Paint Remote Code Execution Vulnerability
by fuzzfactor on Friday November 06, 2026 @12:21PM
(#50395323)
Traditionally tossing excess baggage overboard when the situation gets grim enough.
Like when a previously sturdy old sailing ship starts taking on water, for instance in the 18th century and beyond.
Numerical equivalent to "deep-six."
Re:MS Paint Remote Code Execution Vulnerability
by onei on Friday November 06, 2026 @05:15AM
(#50390478)
Some years ago, I ended up on a call with a support team guy, helping him under some parts of a system I worked on. He shared his screen, started drawing diagrams. It took me a whole 10 minutes to realise it was in paint, he was just that good at using it.
Turns out paint was the thing almost every customer had installed/had access to, so he worked to the lowest common denominator and got really good at using it. I guess now he'll need to find a new tool to astonish devs with.
Re:MS Paint Remote Code Execution Vulnerability
by ethbr1 on Friday November 06, 2026 @06:55AM
(#50391289)
If you're in support across multiple customers, especially in regulated industries, you learn to rely on the minimum common denominator, which usually means OS utils.
And at the end of the day $2 and $2000 screwdrivers are both still screwdrivers.
Re:MS Paint Remote Code Execution Vulnerability
by ndsipa_pomu on Saturday November 07, 2026 @06:11AM
(#50403506)
This is also why knowing the basics of "vi" is so useful on Linux/unix systems
Re:MS Paint Remote Code Execution Vulnerability
by partomniscient on Saturday November 07, 2026 @07:23AM
(#50403938)
...especially knowing how to save/exit without saving/quit, when it automatically opens up for some reason.
Re:MS Paint Remote Code Execution Vulnerability
by joshspankit on Friday November 06, 2026 @09:46AM
(#50392948)
Before MS, there was a time where it wasn’t possible to get a virus by receiving an email. Users had to click on the attachment. Email itself is a text protocol after all.
Then they added automatic HTML parsing of incoming emails, and the attackers cheered.
Re:MS Paint Remote Code Execution Vulnerability
by stevekemp on Friday November 06, 2026 @10:19AM
(#50393381)
Email may be text-based, but parsing MIME is a pain in the ass (speaking as somebody who wrote a console-based email client.)
You can go back to mutt's parsing, and CVE-1999-0940 for an old example. But I'm sure that's only one of many.
Normally have been 86-ing a number of annoying things such as OneDrive, but leaving Paint in place figuring it's got to still be harmless.
Creeping increases in attack vector when just the opposite is needed more than ever.