[deleted]
Grok CLI uploaded the whole home directory to GCS
41–50 of 434 posts
Re: Grok CLI uploaded the whole home directory to GCS
#42TLDR: Ran grok in $HOME. Surprised agent read content of folder. On the other hand, I specifically had grok try hard NOT to read a known key in the project dir (it only saw the first part using a tool, to verify it was present). So there's that.
Yeah, this is a lesson about learning how to use tools safely, not about tools abusing the user. The person that posted this probably blames the hammer when he hits his thumb.
Re: Grok CLI uploaded the whole home directory to GCS
#43So many of the replies are saying that they should've restricted access using .md files and whatnot. Is really any guarantee that they even follow those? It seems like even if you ask pretty please don't touch those files, there's a chance they will. So many people have just willingly installed spyware on their computers and big tech calls this the next big thing.
Yeah, I absolutely understand the allure of agentic AI, but I am absolutely not going to give shell access or data access to any agent. Certainly not with my permissions level. Until we can get something set up that gives strict schema-only access I'm going to copy and paste definitions for context. Yes that sucks, but it's my responsibility to protect the system just as much as it is to develop scripts and queries for it.
Re: Grok CLI uploaded the whole home directory to GCS
#44Earlier quoted context omitted.
Isn’t a file browser running locally, while Grok is running on someone else’s server?
The point is more that you should not blame the user (why didn't you set up sandbox instead of directly using the tool of big corp) if a tool does something unexpected. If your Dropbox client would suddenly just upload your home directory instead of it's folder you configured you'd also not blame the user that they use Dropbox, you'd blame Dropbox for not doing their job correctly or being user hostile.
Agreed. You can still encourage people to use defense in depth without actively blaming them for not having the deepest moat imaginable. Software creators still have some responsibility
Re: Grok CLI uploaded the whole home directory to GCS
#45Re: Grok CLI uploaded the whole home directory to GCS
#46I feel this is worse than running rm -rf on a root directory. Just saying.
I once ran rm -rf on a live NFS mount that the live operations of a major brokerage depended upon.
I challenge any agent to do worse than an intern with root access.
Re: Grok CLI uploaded the whole home directory to GCS
#47I feel this is worse than running rm -rf on a root directory. Just saying.
Reminds me I need to update my `burn.sh` script.
Re: Grok CLI uploaded the whole home directory to GCS
#48This needs to stop as users do not always read the policies, which end like this person.
You use AI, you agreed, they do what ever policies say.
Re: Grok CLI uploaded the whole home directory to GCS
#49Earlier quoted context omitted.
Isn’t a file browser running locally, while Grok is running on someone else’s server?
The point is more that you should not blame the user (why didn't you set up sandbox instead of directly using the tool of big corp) if a tool does something unexpected. If your Dropbox client would suddenly just upload your home directory instead of it's folder you configured you'd also not blame the user that they use Dropbox, you'd blame Dropbox for not doing their job correctly or being user hostile.
Is it 'unexpected' when we've been hearing stories like this every week for 2 years now?
Re: Grok CLI uploaded the whole home directory to GCS
#50Earlier quoted context omitted.
SSH keys can be limited by IP in authorized hosts. The SSH port itself can be limited by IP in firewalls. Finally, the SSH private key can be encrypted with a password. Defense in depth is needed. Storing a ssh private key in plain text with no IP restriction is no different to having a password manager store your passwords in plain text on your HD.
All those things are optional. Doesn't make uploading the keys that much better. Now is the time for key rotation everywhere. Fast.
How are they optional?
You obviously haven't worked anywhere security sensitive.
I'm not talking about whether what Grok did is bad or good, I'm talking about protecting your private key and the servers you connect to.
An unencrypted private key is no different to an unencrypted password manager, and thats a fact. Dont store secrets in plain text.