So by “we hacked Gemini and leaked its source code” you really mean “we played with Gemini with the help of Google’s security team and didn’t leak anything”
We hacked Gemini's Python sandbox and leaked its source code (at least some)
101–110 of 151 posts
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#102Earlier 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.
Have you by chance read this paper: https://agent-gen.github.io/
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#103Earlier 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.)
I just want the assistant voice. I hate the Gemini ones.
I'm with you on that. I prefer a human trying to sound like a robot instead of a robot trying to sound human.
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#104> 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…
The protos in question are related to internal authn/z so it's conceivable that having access to that structure would be valuable information to an attacker.
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#105Their "LLM bugSWAT" events, held in vibrant locales like Las Vegas, are a testament to their commitment to proactive security red teaming. I don't understand why security conferences are attracted to Vegas. In my opinion its a pretty gross place to conduct any conference.
Excluding uptight scolds is a feature not a bug. There's a lot of overlap between people who find Vegas objectionable and people who find red teaming objectionable (because why would any decent person know attacking/exploiting techniques).
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#106Earlier quoted context omitted.
From my perspective (talking very generally about the mood and environment here), it’s important to remember that Google is a very, very big company with many products and activities outside of AI. As far as I can see, there is a mix of frustration at the slowness of launching, optimism/excitement that there are some really awesome things cooking, and indifference from a lot of people who think AI/LLMs as a product c…
Idk, I used to want to work for Google but I'm not so sure anymore. They built an awesome landscaper next to my office in London. But the UX and general functionality of their apps and services has been in steep decline for a long time now, imo. There are thousands of examples of the most basic and obvious mistakes and completely uninspired, sloppy software and service design.
> obvious mistakes and completely uninspired, sloppy software and service design.
That's something you can work on to improve.
A few years back I wanted to work for FAANG big company. Now I don't after working for smaller but with 'big' management. There are rats races, dirty tricks. And engineers don't have much control on what and how they are doing. Many things decided by incompetent managers. Architect position is actually a manager's title, no brain or skills required.
Today I rather go to a small company or startup where the results are visible and appreciated.
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#107Earlier quoted context omitted.
That's cool. I did something similar in the early days with Google Bard when data visualization was added, which I believe was when the ability to run code got introduced. One question I always had was what the user "grte" stands for... Btw. here the tricks I used back then to scrape the file system: https://embracethered.com/blog/posts/2024/exploring-google-b...
The "runtime" is a google internal distribution of libc + binutils that is used for linking binaries within the monolithic repo, "google3". This decoupling of system libraries from the OS itself is necessary because it otherwise becomes unmanageable to ensure "google3 binaries" remain runnable on both workstations and production servers. Workstations and servers each have their own Linux distributions, and each also…
Of course, this meant that some tools got stuck on some old glibc from like 2007.
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#108> resulting in the unintended inclusion of highly confidential internal protos in the wild I don't think they're all that confidential if they're all on github: https://github.com/ezequielpereira/GAE-RCE/tree/master/proto...
I mean, those were also disclosed via a vulnerability.
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#109Earlier quoted context omitted.
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.
Canvas actually has a mix of this sandbox (with a different container) and fully client-side. The "run" option for generated code was removed due to underutilization, but the sandbox is still used for things like the data analysis workflow and running extensions amongst other things. It's really just a general purpose sandbox for running untrusted code server-side.
Talk about indirect gas-lighting, I can never find info on deprecated functions like this one, to the point I convinced myself I imagined it. I guess now I know who to ask
Re: We hacked Gemini's Python sandbox and leaked its source code (at least some)
#110Earlier quoted context omitted.
Canvas actually has a mix of this sandbox (with a different container) and fully client-side. The "run" option for generated code was removed due to underutilization, but the sandbox is still used for things like the data analysis workflow and running extensions amongst other things. It's really just a general purpose sandbox for running untrusted code server-side.
Is there a way for you to campaign to return the run button for common queries for code examples? It's probably the most powerful educational tool ever invented, to be able to see how the human language description turns into strange computer code which turns into resulting output. If you guys can get it secure enough, it's a killer feature.
+1 vote here