Live data from Hacker News

We hacked Gemini's Python sandbox and leaked its source code (at least some)

landh.tech

51–60 of 151 posts

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#51

Earlier quoted context omitted.

I'm on the Google side of the equation. I think the title is a bit sensationalized, but that's the author's prerogative.

When are we going to be able to run sandboxed php code?

You can run PHP in ChatGPT Code Interpreter today if you upload the right binary (also Deno and Lua and more): https://til.simonwillison.net/llms/code-interpreter-expansio...

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#52
I've been using a similar trick to scrape the visible internal source code of ChatGPT Code Interpreter into a GitHub repository for a while now: https://github.com/simonw/scrape-openai-code-interpreter

It's mostly useful for tracking what Python packages are available (and what versions): https://github.com/simonw/scrape-openai-code-interpreter/blo...

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#53

Earlier quoted context omitted.

When are we going to be able to run sandboxed php code?

We could, it's just not high up on the priority list. Any particular reason you want php?

Next step is gemini hosting Personal Home Pages.

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#55
Running the built-in "strings" command to extract a few file names from a binary is hardly hacking/cracking.

Ironically, though, getting the source code of Gemini perhaps wouln't be valuable at all; but if you had found/obtained access to the corpus that the model was pre-trained with, that would have been kind of interesting (many folks have many questions about that...).

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#57

It's actually pretty interesting that this shows that Google is quite secure, I feel like most companies would not fare nearly as well.

Yes and especially the article mentions "With the help of the Google Security Team" so it's quite collaborative and not exactly black box hacking.

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#58
post #21

Earlier quoted context omitted.

They leaked one file in the sandbox that contained lots of internal proto files. The security team reviewed everything in the sandbox and thought nothing in it is sensitive and gave the green light; apparently the review didn't catch this in the sandbox. I guess this is a failing of the security review process, and possibly also how the blaze build system worked so well that people forgot a step existed because it wa…

>that contained lots of internal proto files So does Google Chrome.

No it's not the same level of internal. There are internal proto files specific to Chromium and its API endpoints, and then there are internal proto files for google3. The latter can divulge secrets about Google's general server side architecture. The former only divulges secrets about server side components relevant to Chromium.

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#59
post #37

Earlier quoted context omitted.

Ok, we put the sandbox in the title above. Thanks! (Submitted title was "We hacked Google's A.I Gemini and leaked its source code (at least some part)")

Instead of sandbox can you just make sure people know it was not a meaningful hack? I mean I “hacked” this site too by those standards.

What would be a more accurate and neutral wording?

Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)

#60
post #13

Earlier quoted context omitted.

you re the hacker or the google?

The google

Question: how does it feel inside google in terms of losing their lunch to OpenAi? Losing here is very loose, I don’t think OpenAI won yet but seems to have made a leap ahead of google in terms of marker share and we know google was sitting on tons of breakthroughs and research. Any panicking or internal discontent at google’s product policies? No need to answer if you’re uncomforable that your employer may hold you responsible for what you write here.
Post reply on HN