News for hackers. Stuff that matters.

A comment on Project Glasswing: Securing critical software for the AI era. Parent comment

Re:Project Glasswing: Securing critical software for the AI era by _pdp_ on Tuesday April 07, 2026 @03:57PM (#47680572)
If it is that dangerous as they make it appear to be, 24h does not seem sufficient time. I cannot accept this as a serious attempt.
[ Parent | on HN ]
Re:Project Glasswing: Securing critical software for the AI era by gf000 on Tuesday April 07, 2026 @05:59PM (#47681866)
Well, just prompt it to fix the issue!

/s

[ Parent | on HN ]
Re:Project Glasswing: Securing critical software for the AI era by renewiltord on Tuesday April 07, 2026 @11:01PM (#47684483)
24 h before general internal access seems fine. They don’t have general external access.
[ Parent | on HN ]
Re:Project Glasswing: Securing critical software for the AI era by vasco on Wednesday April 08, 2026 @12:42AM (#47685345)
Time doesn't mean much, what is important is what they did in this 24h. If all they did was talk about it then it could be 1000 years and it wouldn't matter. What are the safety checks in place?

Do they have a honey pot infrastructure to launch the model in first and then wait to see if it destroys it? What they did in the 24h matters.

[ Parent | on HN ]
Re:Project Glasswing: Securing critical software for the AI era by ai5iq on Wednesday April 08, 2026 @11:14AM (#47691378)
Agreed. I've been running autonomous LLM agents on daily schedules for weeks. The failure modes you worry about on day one are completely different from what actually shows up after the agents have history and context. 24 hours captures the obvious stuff.
[ Parent | on HN ]