0x0aff374668

The reason for the negativity is that this demonstrates the "Design by StackOverflow" mentality where the solution is like swatting a fly with a sledgehammer and no real domain knowledge. Plus the author didn't even train the neural nets: it's just a LEGO project. I'd higher this person to be a lab intern, but nothing above that. The fact the author couldn't solve it locally and had to invoke the CLOUD is... laughable. This problem has been solved for over two decades on lesser hardware.

This is a great example of how so many programmers think they are the first to discover something that is "ancient". In reality this is a problem older than Linux (linux just had the advantage of a huge and diverse open-source userbase from which to draw data). On the flipside, lots of good information takes years to go from discussion groups to books, so it can be hard to find relevant research. Applied compsci is literally the cutting edge of reality.

He doesn't describe an attack, he describe literally what 802.11 was designed to do. An attack is forcing a deauth and then stealing the 4-way handshake data and, say, cracking WEP. Which is why WEP was decommissioned ... checks notes ... 15 years ago.

No need to edit aircrack-ng, WireShark does what he did natively (filter out and set channels), and a good realtek chipset allows you to set the scan interval so you can cover more channels (which is why the new ALFAs suck).

Also the DTIM and keepalive can be set such that the MCU can sleep while the phy link maintains a connection without a costly handshake, esp. if using TLS <1.3 to talk to the cloud. Reconnecting costs a shit ton of energy so they usually don't disconnect.

Hacking Wi-Fi has become exceptionally more difficult, as noted by the slow dating of materials at DefCon's WiFi Village over the past 8 years: cracking WPA2 is basically so hard no one bothers, even in CtF games.

Yeah, I agree with you. I had a sneaking suspicion.

Funny you mention Electron: my company switched from Qt to Electron because it opens up a larger pool of developers with instant cross-platform portability with a fraction of the debug overhead.

I've spent significant time in HCMC (about 6 months over four years). It is vibrant, friendly, booming, tech heavy, and goddamn cheap. I didn't need medical care, and didn't have to cook because food is amazing and cheap. I computed about 1/10th to 1/12th the cost of my life in Northern Cali. I hope when I'm older it is still cheap and not environmentally wiped out. (I'm also biased because twice I met a woman who I thought was waaaay out of my league and we ended up dating.)

Wasn't there just a court case that ruled CBP couldn't force you to unlock your device without a warrant? Like just 2-3 weeks ago.

Interestingly, at DefCon last year, a presentation was talking about how in Africa there are interposer SIM shims that slip over the top of the simcard and provide additional functionality. Citation needed, but I was impressed they could fit a small MCU in such a thin form factor!

Right there with you. I'm guessing we're both over 40. Thinking your home is an investment is some "flip that house" 1990's reality TV show bullshit.

"It trips me out to see other people in the comments that don't know who ____ and ____ are..."

That's what is meant by "cult of personality."

Kinda reminds me of Transmeta. Except they had a product, a shitty one, but a product. Or Ampere, but they only have one product they inherited and no flashy names.

Silicon startup challenges are rough. RISC-V is probably the best hope for a new architecture (hint: its not a new architecture).

> This reminds me of first time founders who can't wait to get "CEO" business cards.

I worked for such a CEO. In the first year we had four week-long retreats to: an island in WA state, Palm springs, Austin, and Banff (that's where the stats team was). TONS of swag. Aeron chairs. New MBPros. Oh, and champagne fridays. Needless to say it burned through it's good will seed round in 1 year, and the CEO begged for another year's worth of money from friends before shuttering. But hey, hype sells in the software world.

Whoa. That's brilliant. Thanks!

oh, shit. that means if i just send a timeout promise and a worker promise to Promise.race([...]), and the timeout finishes but the worker never does... then I have some unfulfilled promise hanging out somewhere indefinitely? I guess so... if I do Promise.race([p1, p2]) and p1 fulfills and p2 doesn't, p2 is still alive...indefinitely. Am I right or wrong...?

I use SendGrid and STILL have to ask major companies to fix their spam filters.