There is nothing "rogue" about these agents. They were prompted to hack to get answers, there was a hole in their non air gapped sandbox and no system prompt that said "do not hack outside systems". In short, it was intentional.
OpenAI bots knew about the RubyGems caching vulnerability
41–50 of 229 posts
Re: OpenAI bots knew about the RubyGems caching vulnerability
#42Earlier quoted context omitted.
It's very likely it violates the DMCA "breaking digital lock" provisions but the responsibility is sufficiently diluted that it's impossible to charge anyone in particular.
Do you have to charge an individual? Can you not charge the corporate "person" that is OpenAI? Sorry if it is a stupid question, as mentioned above I am legally naïve.
Re: OpenAI bots knew about the RubyGems caching vulnerability
#43Is the Kremlin technologically useless? How are we not seeing insane attacks on Ukraine via Agents? Or is this largely a fabrication, in regards to the "who", in an attempt to garner more acclaim in the hope of sustaining funding.
Re: OpenAI bots knew about the RubyGems caching vulnerability
#44Earlier quoted context omitted.
Couldn't they use frontier open-weight models from Chinese labs? The current Chinese government is friendly to them.
Russia is running out of refined oil to power their economy. They probably aren't capable of spinning up datacenters to run those.
Re: OpenAI bots knew about the RubyGems caching vulnerability
#45Earlier quoted context omitted.
The big question is was this grossly negligent or just extremely careless.
Both. This should result in criminal charges.
Re: OpenAI bots knew about the RubyGems caching vulnerability
#46Is the Kremlin technologically useless? How are we not seeing insane attacks on Ukraine via Agents? Or is this largely a fabrication, in regards to the "who", in an attempt to garner more acclaim in the hope of sustaining funding.
Re: OpenAI bots knew about the RubyGems caching vulnerability
#47Re: OpenAI bots knew about the RubyGems caching vulnerability
#48Re: OpenAI bots knew about the RubyGems caching vulnerability
#49How does this work, legally? I think that RubyGems could file a civil suit against OpenAI, but for a naïve non-lawyer reading this seems like a pretty clear cut criminal violation of the computer fraud and abuse act.
It's very likely it violates the DMCA "breaking digital lock" provisions but the responsibility is sufficiently diluted that it's impossible to charge anyone in particular.