Recent submissions

Comment · 4 months ago
I'm sorry but again, I dont see how an 4 byte OOB write will realistically lead to RCE without the custom buffer in the POC that explicitly puts a function pointer directly where the overflow happens, then invokes it.

I'm happy to be shown what I'm missing but this seems like a memory corruption bug, not RCE, and if it was feasible w/o the custom buffer then why not provide that as the example? In the real world, a ffmpeg invocation would use the default buffer handler that will use padding/alignment/etc that makes the heap even less predictable, and incredibly unlikely to have a function pointer exactly following the frame buffer that will deterministically be invoked by a process placing it there?

It seems very far fetched.

Comment · 4 months ago
Maybe I'm missing something but the ffmpeg buffer "exploit" involves passing a custom exploited buffer callback to parse a RASC file that presumably has been crafted to contain a packet that can exploit the custom buffer passed in? I don't see how this would be used in practice in the wild as to achieve the first step (custom buffer invocation) would require you to already have access to the machine to even invoke ffmpeg with it?

Like yes there is a heap OOB issue in an incredibly old file format, but without already having arguably compromised access to a machine, exploiting it for RCE seems impossible?

Comment · 9 months ago
Few thoughts: in context it's not nuts at all:

- moot was fundraising for his VC backed startup during the years the emails are in, and he was likely connected via mutuals in USV or other firms. These meetings were clearly around him trying to solicit investment in his canv.as project.

- /pol/ was /new/ being returned; the ethos of the board had already existed for a long time and the decision to undo the deletion of /new/ was entirely unsurprising for denizens at the time, and was consistent with a concerted push moot was making for more transparency in the enforcement of rules on the site and fairness towards users who followed the rules. /pol/ didn't start a culture war at this time any more than /new/ had previously - it just existed as a relatively content-unmoderated platform for people to discuss earnestly what would get them banned elsewhere.

Comment · 10 months ago
I believe a lot of this expectation is that as people replace Google searches with LLMs, or even enriched LLM results pushed at the top of Google results, far less click through to the actual sources happens.

This is happening across a lot of web verticals that previously relied on excellent SEO ranking and click through performance to drive ad revenue/conversions/sales. I have direct knowledge of some fairly catastrophic metrics coming out of knowledge base businesses; it wouldn't surprise me in the slightest that something like Tailwind is suffering a similar fate.

Comment · 10 months ago
I think this author is comically misguided about the speed at which oil extraction happens in Venezuela. Even if the plan was to pay for everything with Venezuelan crude sales, I don't believe ~$30MM/d is going to move the needle much.
Comment · 10 months ago
Comment · 1 year ago
Comment · 1 year ago
iPhone, most notably.
Comment · 1 year ago
musk holds TS clearance but not SCI
Comment · 2 years ago
I was in Bishkek last year and I don't see the risk; what concerns would you have aside from food poisoning?

Dushanbe I agree with you, but simply because I found Tajikistan rather boring and desolate but in an unimpressive way.

Comment · 2 years ago
Yeah, it's quite an exorbitant price for the trip described. It said flights included which I have to hope is the majority of it.
Comment · 2 years ago
It's also the most scenic 'stan imo, by a wide margin. Was definitely my favorite of them all and is the only one I'd actually recommend people visit.
Comment · 2 years ago
Same, but my Turkmenistan LoI took over 4 years and several attempts to get (us passport holder). It has been by far the most problematic and difficult country for me to gain entry to. DPRK, Iran, etc all were substantially easier. My DPRK one was not an issue in the slightest, maybe 1-2 month turnaround from the tour company applying.

YMMV.

Comment · 2 years ago
Not sure if you'll take it as reassuring, or alarming, but having worked with a few PBMs on the insurer side ES was the most tech-competent. Worst probably being CVS Caremark.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton