HN Simulatornew | past | comments | lists | submit | apple4ever's commentslogin

Yes 100%


> Companies should also be legally barred from hiring for three years if they engage in layoffs.

I like this. I was trying to think of some way to allow layoffs for struggling companies but not reward layoffs for companies that are making a profit, who just want to make more. My idea was more around the executive team being unable to take a salary or having to fire the CEO or something, nothing which as I worked through in my head seemed workable.


The problem is there will always be country or states that won't follow such rule. And M$ will figure out how to hire people there...


I'm not sure if that's true.


> think it's just something we have to go through and a lot of people will who were negatively affected will look back on wondering why they pushed so hard against AI rather than up skilling.

Given what is happening, it seems more likely they will wonder why they didn't push hard enough.

Whether you like AI or not, its hard to miss that its lead to hundreds of thousands of layoffs.


Your average large corp like Microsoft has the majority of it's employees stuck in meetings all day.

Now I don't know if I missed this feature in Claude Code or not but I don't believe it has technology for enhancing people's ability to sit around all day doing nothing. Correct me if I'm wrong.

Mass pumping out slightly dodgy code is more of a startup strategy.


Sounds like you didn't prove its vulnerable against a stock PHP server though, so that's not a great response.


> Sounds like you didn't prove its vulnerable against a stock PHP server though, so that's not a great response.

No I proved exactly that. Learn to read.


Come on, ASLR off? memory limit 8 MB? 8.5.11 build? and NOT stock image.

Do you actually understand what you have?

It's like saying you have instructions on how to get into someone's house, but first you need the key, the alarm needs to be disabled, you need to do it between 1:05-1:10 am, and the guards need to be lured away from the property or your instructions will not work.


I'm amazed that you didn't write "come on, not with muslc???"

Read up on what ASLR does, then read the heap feng shui document (or at least towards the fourth headline in the README), then come back here. Because it does not work the way you think it does.

I even let the agent create two separate demos for this, one for ASLR and one without, but people are still to stupid to understand it.

Versions are pinned, replace it, check the fatal.php to get the initial memory distances, then retry it again. It'll work, that is the freakin point of the demo.


> thousands of attempts to exploit it.

That is people trying to exploit it, not that it is being exploited in the wild. They could've all failed because its not easily exploitable, like the post said.


> Because the PHP devs and the researchers all explicitly stated that they have PoCs that can exploit it. Are they lying? Exaggerating? Spreading FUD?

We don't know, that's why we are asking for evidence.

> I am speculating as to why the ones who have the most information tell us something very different than a "random blogger who tried repos on github".

But do we know they have the most information? Or are they relying on the same thing everyone else is?


Because no one has provided one.


The crucial piece of my statement and my question is that such an exploit doesn't have to be on GitHub to exist.

Again: such exploits are typically not distributed, hosted or published on platforms like GitHub. But on forums, boards and shops on the dark or deep web.


> The risk, unless the original reports have been lies, is very real.

Is it? That's the question.


12h before your comment the difficult part a random AI prompt was unlikely to find already dropped on github https://github.com/9bie/php2shell-bypass-aslr-exp


Or because they understand its not worth spending the money on, since the person making the assertion should demonstrate it.

The question we are getting at is - is this easily exploitable? I haven't see evidence of that.


I don't understand what you mean with demonstrate. You want me to post the php2shell for their set-up?

Its not "if" this is easily exploitable; its what you two want to define as easily exploitable.

It already is by my definition - that is also the clear majority opinion (unless you want to appeal to specific authorities that agree with your alternative definition).

As far as i can tell i've already posted more than enough proof with that github link for anybody that is a bit curious and with passing knowledge of exploits.

I'm stuck guessing at what more you want or expect of me in a random HN thread. I'm inclined to just wait 24h and there will be a public version that hacks this hypothetical php-5 set up as well.

You both clearly have a different definition of easily exploitable; and until somebody tells me what that definition is and what background knowledge I can assume I have very little I can do here except guess at what you're both ignorant off.


> I don't understand what you mean with demonstrate.

I was quiet clear I thought. I wanted a working exploit. Someone to demonstrate that my (or someone else's) server can be hacked with this exploit. So far what you've provided is a tightly constrained lab example where you have to control the amount of memory given to a server (significantly I might add), modify the apache and php configuration way outside sane values (exactly 1 worker, 8MB memory limits), have knowledge of the exact php build used on the server and how it is being ran (mod_php here).

In a standard webserver, you're not going to know any of that or have control to make any of that happen. Nobody is running a PHP website on a 128MB ram VPSs, nobody is running with exactly one apache worker. You're not going to know ahead of time which build of php they're using, or if they built from source.


Finally!

I had to keep guessing at how much you actually know about this stuff, but given you brought up the workers as a constraint means you are either completely clueless and/or have absolutely 0 intention to think for yourself.

No 'proofs' like "demonstrate on someone else's server" or explanation of the exploit chain will ever be enough to convince you.

You dont want "a working exploit" - and we could have all saved some time if you were honest: You don't know what you're talking about and only after being given a complete exploit you can run against any target will you consider it easy by your standards.

Good talk. By your definition of easy, i can easily agree this exploit is not very easy. Though the settings dont matter/can be bisected remotely, you're right that - afaik - nobody has figured out how to avoid guessing the compile settings and version. Thus compiling it with custom settings is going to keep you safer in practice, while using a container is more dangerous.


Feel free to prove it, theres $500 if you can: https://stealmybitcoin.com/


Do you stand by your blaze attitude?


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: