Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

landh.tech

Post reply on HN
Print view View original

131–140 of 151 posts

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

#131

Post by ryao »

o11c wrote: post #128
ryao wrote: post #127

Earlier quoted context omitted.

If you are making sandboxes, you need to put the files in place each time. With ZFS clones, you can keep referencing the same files repeatedly, so the amount of changes to memory needed to create an environment are minimized. Let’s say the sandbox is 1GB and each clone operation does less than 1MB of memory writes. Then you have a >1000x reduction in writing needed to make the environment. Furthermore, ZFS ARC should…

It's worth noting that if you go down a layer, LVM snapshots are filesystem-independent.

You need to preallocate space on LVM2 for storing changes and if it fills, bad things happen. You have write amplification of 4MB per write by default on LVM2, while ZFS just writes what is needed, since LVM2 isn't aware of the filesystem structures. All of the advantages WRT cache are gone if you use LVM2 too. Correct me if I am wrong.

That said, if you really want to use block devices, you could use zvols to get something similar to LVM2 out of ZFS, but it is not as good as using snapshots on ZFS' filesystems. The write amplification would be lower by default (8KB versus 4MB). The page cache would still duplicate data, but the buffer cache duplication should be bypassed if I recall correctly.

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

#132

Post by IshKebab »

paxys wrote: 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.

They didn't even hack it.

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

#133

Post by lanyard-textile »

nikcub wrote: post #68
onemoresoop wrote: post #60

Earlier quoted context omitted.

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…

Nobody serious believes this. OpenAI may be eating up consumer mindshare - but Google are providing some of the most capable, best, cheapest and fastest models for dev integration.

I’m honestly shocked to hear anyone defend gemini, respectfully :)

What casts it as most capable?

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

#134

Post by simonw »

12345hn6789 wrote: post #119
Zopieux wrote: post #91

Earlier quoted context omitted.

Meanwhile they could just decide to publish this list in a document somewhere and keep it automatically up to date with their infra. But not, secrecy for the sake of secrecy.

What would the benefit of doing this be?

It's documentation. Makes it much easier for people to know what kind of problems they can solve using Code Interpreter.

It's a bit absurd that the best available documentation for that feature exists in my hacky scraped GitHub repository.

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

#135

Post by saagarjha »

Brian_K_White wrote: post #124
saagarjha wrote: post #108

Earlier quoted context omitted.

I mean, those were also disclosed via a vulnerability.

But it still means they aren't guilty of leaking/disclosing them. It's not a valid point of criticism. The escape did not in fact "result" in the leak of confidential photos. That already happened somewhere else. This only resulted in the republishing of something already public. Or another way, it's not merely that they were already public elsewhere, the imortant point is that the photos were not given to the ai in…

I’m not criticizing them

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

#136

Post by Brian_K_White »

saagarjha wrote: post #135
Brian_K_White wrote: post #124

Earlier quoted context omitted.

But it still means they aren't guilty of leaking/disclosing them. It's not a valid point of criticism. The escape did not in fact "result" in the leak of confidential photos. That already happened somewhere else. This only resulted in the republishing of something already public. Or another way, it's not merely that they were already public elsewhere, the imortant point is that the photos were not given to the ai in…

I’m not criticizing them

The article made that criticism.

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

#138

Post by Brian_K_White »

saagarjha wrote: post #137
Brian_K_White wrote: post #136

Earlier quoted context omitted.

The article made that criticism.

The article criticized its authors? I’m not sure I understand.

The article / leak authors said that the leak resulted in the exposure of highly confidential protos.

I was saying that the article was wrong for saying that, but I was half wrong about that.

I thought that the thing they were talking about was something that the AI got from a public source, in which case the AI didn't disclose anything it was given in confidense. It just republished something that it itself got from a public source in the first place.

Except I think I had that wrong. The stuff was already published elsewhere, but that's not how the AI got it. The leak caused the AI to disclose some of it's own internal workings, which is actually a leak and does "result in the disclosure of something confidential" even of something else elsewhere had already also seperately disclosed the same thing. That other leak has no bearing in this case.

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

#139

Post by GrayShade »

7bit wrote: post #28
Mindwipe wrote: post #10

Earlier quoted context omitted.

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.

Just tested, you need to enable "Gemini Apps", but they remember your interactions for 3, 18 or 36 months instead of 3 days.

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

#140

Post by 7bit »

GrayShade wrote: post #139
7bit wrote: post #28

Earlier quoted context omitted.

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.

Just tested, you need to enable "Gemini Apps", but they remember your interactions for 3, 18 or 36 months instead of 3 days.

Yeah, I disabled that when I tested it. No go for me, but thanks for informing me!
Post reply on HN