Live data from Hacker News

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

landh.tech

21–30 of 151 posts

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

#21
post #12

They hacked the sandbox, and leaked nothing. The article is entertaining though.

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 was too automated.

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

#22
post #9

Funny enough while "We hacked Google's AI" is going to get the clicks, in reality they hacked the one part of Gemini that was NOT the LLM (a sandbox environment meant to run untrusted user-provided code). And "leaked its source code" is straight up click bait.

Click and cash (for the great trio).

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

#23

That's the system I work on! Please feel free to ask any questions. All opinions are my own and do not represent those of my employer.

Does anyone at Google care that you're trying to replace Assistant with this in the next few months and it can't set a timer yet? (I mean it will tell you it's set a timer but it doesn't talk to the native clock app so nothing ever goes off if you navigate away from the window.)

The Assistant can't reliably set timers either, though I guess 80% is considerably better than 0. Still, I think it used to be better back before Google caught a glimpse of a different squirrel to chase.

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

#24
post #7
post #2

> However, the build pipeline for compiling the sandbox binary included an automated step that adds security proto files to a binary whenever it detects that the binary might need them to enforce internal rules. In this particular case, that step wasn’t necessary, resulting in the unintended inclusion of highly confidential internal protos in the wild ! Protobufs aren't really these super secret hyper-proprietary thi…

No, but having the names to the fields, directly from Google, is very helpful for further understanding what's available from within the sandbox.

Reminds me of this HN article from a month ago with lots of commentary on whether a database scheme is proprietary.

https://news.ycombinator.com/item?id=43175628

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

#26

Earlier quoted context omitted.

Is the interactive python sandbox incompatible with thinking models? It seems like I can only get the interactive sandbox by using 2.0 flash, not 2.0 flash thinking or 2.5 pro.

That's a good question! It's not incompatible, it's just a matter of getting the flow right. I can't comment too much on that process but I'm excited for the possibilities there.

Oh, I see Gemini can run code as part of the thinking process. I suppose the sandbox that happens in was the target of this research, while code editing in Gemini Canvas just has a button to export to Colab for running. The screenshots in the research show a "run" button for generated code in the chat, but I'm not seeing that exact interface.

In any case, I share your excitement.

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

#27
post #2

> However, the build pipeline for compiling the sandbox binary included an automated step that adds security proto files to a binary whenever it detects that the binary might need them to enforce internal rules. In this particular case, that step wasn’t necessary, resulting in the unintended inclusion of highly confidential internal protos in the wild ! Protobufs aren't really these super secret hyper-proprietary thi…

[deleted]

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

#28

That's the system I work on! Please feel free to ask any questions. All opinions are my own and do not represent those of my employer.

Does anyone at Google care that you're trying to replace Assistant with this in the next few months and it can't set a timer yet? (I mean it will tell you it's set a timer but it doesn't talk to the native clock app so nothing ever goes off if you navigate away from the window.)

It can't do shit, especially in some EU countries, where it can do even less shit.

Setting timers reminders, calendar events. Nothing. If they kill the assistant, I'll go Apple, no matter how much I hate it.

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

#29

That's the system I work on! Please feel free to ask any questions. All opinions are my own and do not represent those of my employer.

Does anyone at Google care that you're trying to replace Assistant with this in the next few months and it can't set a timer yet? (I mean it will tell you it's set a timer but it doesn't talk to the native clock app so nothing ever goes off if you navigate away from the window.)

I keep reading people complaining about this but I can't understand why. Gemini can 100% set timers and with much more subtle hints than assistant ever could. It just works. I don't get why people say it can't.

It can also play music or turn on my smart lamps, change their colors etc. I can't remember doing any special configuration for it to do that either.

Pixel 9 pro

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

#30

Earlier quoted context omitted.

Do you think "hacked Gemini and leaked its source code" is an accurate representation of what happened here?

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?
Post reply on HN