So I took that RDP vuln checking tool and cleaned it up, so it produces more diagnostic info, runs on macOS/Windows/Linux, scans lists of IP addresses and ranges, runs through SOCKS5/Tor, and other stuff.
I'm currently running it on the results from 'masscan 0.0.0.0 -p3389", but my guess is that only around 30,000 machines on the public Internet are vulnerable. It's going to take a day to run, because rdpscan is a lot slower than masscan.
In other words, only about 1% of those machines responding on port 3389 come back as 'vulnerable'.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
It's probably biggest in Economics, where it's hard to have a rational discussion about what DOES happen because people are so concerned with what SHOULD happen.
It's a lot easier with physics or chemisty.
It's a big problem with law. There's a wide gap between what the CFAA DOES day and what people think it SHOULD say.
Infosec was up in arms that F12 "view-source" isn't criminal hacking, but that was a NORMATIVE statement. Nobody read the Wisconsin law to see what it DOES say.
Back a couple years ago, people were rewriting the classic 'wc' program (word-count) in their favorite programming language to prove theirs could be as fast as C.
So I decided to rewrite using my favorite algorithm instead: a "state machine parser".
The algorithm to count words (and lines and characters) is 3 lines long, the while(){} loop at line 25.
You are supposed to marvel at how this is absolutely NOT a word/line/char counting algorithm -- and yet, it produces the same results as 'wc'.
I implemented the same algorithm in JavaScript, and it ended up being faster than all those "I rewrote wc in my favorite language" examples. But the reason isn't that JavaScript is faster than their language, but because the ALGORITHM is faster. It also jits well.
About an hour into it, when I'm describing DNS header compression on generating the query packet for "google.com" that they'll be asking me politely to leave.
I lie. It'll take hours to get to that point, as I first explain how Chrome caches DNS names before making a request to the operating system to do DNS resolution on it's behalf -- assuming they haven't enabled DNS-over-something.
I lie. There's probably a whole day's discussion of what happens when you click with the mouse on the screen to load the page, tracing the path of execution through Windows event handlers.
Note that I'm not a solid source here. 1. I experience weird disruptions trying to make calls to the Ukraine cell phone network 2. Techies (who don't want to be named) said it was because the cell network was being DDoSed.
I do know that while cell providers are supposed to have private links to each other, I know that a lot of traffic ends up going across the Internet backone, so the scenario is plausible (though not proven).
The weirdest thing was a recorded message saying the subscriber wasn't available, in english, but breaking up severely due to disruption on the network, which as I understand it, shouldn't be possible.
Here is inflation from the Eurozone. It has the same spike as we do. It's hard to imagine how Biden caused that.
The things that economists cite that cause the current inflation were the steps taken during Trump's administration. Stimulus happened in 2020, the effects were seen in 2021. It was sticking upwards before Biden had a chance to make any difference.