This is a glorified IPS, and those in the know are aware of how ineffective such systems are. You might stop a few skiddies attacking the internet en masse, but this is a speed bump for anything remotely close to an advanced persistent threat.

I was losing sleep over this.

An assembler is a program that translates assembly into object code. Assembly is the language.

I'm sick of all that advertising on Wikpedia. Oh wait

You don't get me, huh? Perhaps I need to be a bit more explicit: I don't give a shit what you use, but if start spewing vitriolic claims about a given technology, you'd best be adequately informed so that you can defend said claims. In this instance, your unsubstantiated, shallow assertions attracted the attention of a Powershell user, who challenged them. You failed to provide anything of substance indicating that "Powershell is a joke", making you look like yet another zealot who disregarded it for religious reasons. To reiterate: your choice didn't bother me, it was your attempt to position yourself as some sort of expert.

You haven't provided a single concrete example of what you can easily achieve with the Linux CLI that can't be done with PS. Both have their obvious strengths and weaknesses, so doing so shouldn't be hard. It makes me question your competency, you know? In fact, the only example you've given makes me want to vomit. You think that is elegant or intuitive? Fuck man. But yeah, I actually do work with servers, being that I do a lot of work with distributed computing. In fact, I specialize in distributed test automation, so I'm getting a laugh out of your lone, pitiable example.

Nope, too vain to post as AC, AC.

IPC is possible, albeit differently than Linux. Is this alone enough to discount Powershell entirely? Perhaps if you're a zealot. Personally, I prefer the object oriented nature of PS to the hacky string parsing of the Linux CLI. I write enough string processing code as it is, I'd rather not write anymore performing menial tasks. Taking a dependency on a blob of text is generally a bad idea, and that's precisely why PS' approach is so elegant.

Anyway, if you genuinely recommend WSH over PS, you can be safely disregarded.

Your mentioning of findstr and robocopy, two tools completely unrelated to Powershell, make it apparent that you're either disingenuous or completely ignorant of what Powershell is.

What are you blathering about? I was correcting his misuse of the term "exploit". Vulnerability and exploit are often used as synonyms, but they're not.

I think you're confusing read overruns with more general read access violations. If you're trying to predict valid addresses, sure, you're probably going to crash the program with a read AV. However, a read overrun implies that the read begins in valid memory, so unless you hit a guard page or something while reading off the end of the buffer, you're probably in the clear.

Competent programmer here. Exploits are programs developed to take advantage of flaws and vulnerabilities, so most software is not "stuffed" with them. Anyway, the post I was responding to seemed to be insinuating that bugs like this go unfixed in proprietary software simply because it is proprietary. I can tell you that is not that case. There are researchers out there combing through everything, open or closed.

This is a read overrun, so ASLR won't save you. Ignore the guy above who posted about ASLR bypasses--that's not really relevant to this.

Got any actual evidence, or are you simply going to try to deflect blame away from this glaring black eye?

Don't use Java and its shitty VM; there are better managed languages out there.