Project Glasswing: what Mythos showed us
blog.cloudflare.com
Project Glasswing: what Mythos showed us
1–10 of 152 posts
Re: Project Glasswing: what Mythos showed us
#2That's great and all but how severe were the most severe vulnerabilities found? I imagine they don't want to talk about it, but that's really the most interesting and important bit.
Re: Project Glasswing: what Mythos showed us
#3The real question is whether it was Mythos or Opus that wrote this post.
> "Why it matters"
It doesn't, it's a corporate blog, they were rarely written in one-author's voice anyway, but it's interesting to see that even large organisations are outsourcing their blogs to LLMs.
Re: Project Glasswing: what Mythos showed us
#4That's great and all but how severe were the most severe vulnerabilities found? I imagine they don't want to talk about it, but that's really the most interesting and important bit.
Most of their new products are AI tools that nobody uses, so I guess they’ll keep posting slop. And recently, they’ve fired so many people that they probably don’t have good writers anymore.
Re: Project Glasswing: what Mythos showed us
#5I can't wait to be told that Cloudflare is now part of "The Mythos FUD" campaign.
Re: Project Glasswing: what Mythos showed us
#6great, but why don't you share real data on how many security vuln it found ? how many were reals, how many weren't ?
Re: Project Glasswing: what Mythos showed us
#7The real question is whether it was Mythos or Opus that wrote this post. > "Why it matters" It doesn't, it's a corporate blog, they were rarely written in one-author's voice anyway, but it's interesting to see that even large organisations are outsourcing their blogs to LLMs.
This looks more like it was edited by AI rather than fully written by it. Or they are using a really good humaniser for the second pass.
Re: Project Glasswing: what Mythos showed us
#8Beside the poorly written post, the vulnerability discovery workflow might actually give good results
Re: Project Glasswing: what Mythos showed us
#9Interesting for teams looking to implement ai into their deployment process.
I don't think guardrails are useful long term. Assuming we don't see the end of open near-frontier models, it is folly to try to keep models from doing exploit generation. The solution needs to be all software projects writing code under the assumption that hackers will be running LLMs against their code in search of exploits and write secure code accordingly.
Re: Project Glasswing: what Mythos showed us
#10The real question is whether it was Mythos or Opus that wrote this post. > "Why it matters" It doesn't, it's a corporate blog, they were rarely written in one-author's voice anyway, but it's interesting to see that even large organisations are outsourcing their blogs to LLMs.
It's fascinating seeing people think that if you're snarky enough about something, the substance of that thing actually ceases to be substantive.
It's like staring down the barrel of a gun and taking the time to make quips about the type of paper the gun advertisement was printed on.