Speaking from experience, the LLM agents adapt fairly well to these contexts too. It's not at all FUD, you're at a significant disadvantage if you don't compete with AI now. I went to a CTF recently against teams I have won against every year, and within 10 minutes of the event starting they had solved every challenge. They have an agent loop and it solves everything immediately, so they won. Anyone attempting to solve the challenges on their own has no chance, even if you think "maybe this is too out of the box for LLMs". Furthermore, the DEFCON CTF you're referring to has quals, and if you don't qualify you don't get those challenges in the finals. Quals has mainly binary exploitation challenges which Opus (and others) solve as long as you hold the gas pedal down on your API bill. I don't believe it's hyperbole to say CTF is dead, as a competitor.

I can't even sign up for Max (last tried yesterday), their credit card processor has issues.

Another trope: longer README.md's than anyone would make, or want.

Yes, to me this is a huge tell. Especially when it goes into detail about pros and cons (using a table) on the most superficial points.

and all those emoji... sometimes to the point they are on most lines and commit messages.

I prefer the Dell Rugged line or Thinkpads, since a single water droplet on the keyboard is enough to kill this laptop.

???

I do dishes with an MBP next to the sink. I wouldn't put it under the faucet, but it's ~fine so far.

I wouldn't if I were you. Indeed there's a membrane that can keep drops away from electronics, but one big drop will find a way eventually. Doesn't even have to be a spill. Macs are infinitely fragile actually, there is zero effort spent on moisture or even dust intrusion.

> infinitely fragile

At last check my 2008 unibody still boots. It can vote in the fall.

Did this happen to you? I was under the impression that a tiny spill was no longer fatal for Mac laptop keyboards. I've seen it happen a few times and be fine, but maybe the people I knew were just lucky?

The new Apple keyboard seems to fix itself. Once my command key had fallen down. It actually fixed itself somehow. I think it’s got whatever miracle metal snaps back into shape in there. And my kid has been using my old laptop and leaving crumbs; when a crumb gets under the key you feel it, but just press it in and destroy the crumb and the key is fine.

I remember the old keyboard because I got so sick of it I snapped the laptop in half in a rare fit of disgust (I was under a lot of stress at the time).

Overall, Apple blew it out of the park, and I happily forgive the earlier problems. Now I hope that Tahoe is just some kind of planned demolition phase before they introduce a totally new unsurpassable stable OS.

In a moment of brain fog I forgot laptops have a hinge, and I imagined you to be the strongest person in the world.

I hate thinkpads. I was a traveling consultant for nearly a decade. I had three thinkpads and two completely broke within 2 years. The third was ok but when replaced with a MacBook pro I became an apple convert.

Also the Kiisu which is 1:1 with capabilities, plus a few more.

I made a site to use LLMs to help me with reverse engineering. The output is surprisingly readable, even with C++ classes. Let me know any feedback you might have: https://decompiler.zeroday.engineering/

This is great! With Ghidra I had to look for the corresponding libs of a very specific RiscV vendor, your SRE did it by itself. You should have your own HN thread in front page!

What kind of file should be uploaded?

The allowed types are a bit misleading. Any binary is accepted, any architecture. You can upload shared objects, ELF executables, PE binaries, etc.

I like to give it bomb executables (reverse engineering challenges) to test it.

> Any binary is accepted, any architecture.

One should be careful tossing around the word "any" in relation to executable formats, for there are seemingly an unbounded number of them: https://github.com/1Password/onepassword-sdk-go/blob/v0.1.5/...

Up to you, but currently your polling endpoint just has a boolean, which is likely super easy to cook on the server side but also leads the user left wondering "uh, is this thing on?" in ways that any kind of percentage might not. IOW, how long, exactly, should any sane person wait for it to be {"status":true}?

Also, you have your ELB misconfigured because trying to upload a binary that is takes more than 30 seconds to upload causes the actual POST to puke. I'm sure that's great for hello-world.exe but is absolutely hilarious for any real binary

I can answer the writing to /proc one. It is sometimes useful to hotpatch running programs with /proc/pid/mem.

And that's what I'm getting at, and where I'd like the community to improve in discussions. In what context do you need it, and how much, and what would your alternatives be?

Because, the amount of different contexts linux is being used in, and the different threat levels are vastly different.

For example, I'm aware that the industrial and embedded world does wild things at times. Because it's hard to establish redundancy and replacability there. Because the system is attached to a $750k lathe. However, that thing is not networked, and physical access is controlled by people with guns. Do whatever you need to keep this thing running, as horrid as it may be.

On the other hand, I have a fleet of loadbalancers and their job is to accept traffic from all criminals in this world, and then some legitimate users as well. I can reset them to base linux and have them back operational in 10 minutes or so. Things modifying loaded code in memory outside of some very specific situations like service startup on these systems is terrifying and entirely not necessary.

So I would be very happy with a switch to turn that off, even though some other use cases wouldn't need it or wouldn't be able to use it at all.

Or the LilyGO T-Embed CC1101.

CC1101 boards(at least the cheapest ones) have problems with shared SPI bus(SD card and Subghz module)