Reactions
32 postsGO 
Gergely Orosz@GergelyOroszCannot see any sensible company use Grok CLI based on this terrible incident If you are an amateur (meaning you don't make much or any money from your code) and do not care about security (aka you don't mind if your .env files leak - which you should care about) then use it…
- likes: 762
- replies: 48
- bookmarks: 70
- reposts: 52
GO Gergely Orosz@GergelyOroszSill baffled at this response from Grok / SpaceX: which is basically: "if you use Grok via API we did not upload your files [we could not], and if you are an enterprise customer, we promise we do not do what we do with everyone else")…
- likes: 92
- replies: 4
- bookmarks: 2
- reposts: 4
GO Gergely Orosz@GergelyOroszThe proposition from Grok is basically: "Use us if you are happy and willing to rotate your .env files after you use our CLI" That's how bad this is, and how Grok never ever addressed uploading the .env files to a GCP container Speaking for myself I'll skip any harness doing…
- likes: 78
- replies: 5
- bookmarks: 1
- reposts: 3
GO Gergely Orosz@GergelyOroszTHIS is the problem… Grok uploaded the unencrypted .env files not from the repo but your local folder…. https://twitter.com/inner_concerns/status/2076935210030248007
- likes: 42
- replies: 4
- bookmarks: 1
- reposts: 1
CE Carlos E. Perez@IntuitMachineGPT-5.6 rumoured to delete entire folders... Now Grok found to be uploading entire directories?! WTF is going on? https://twitter.com/IntCyberDigest/status/2076689215258014069
- likes: 15
- replies: 3
- bookmarks: 4
- reposts: 4
“P “paula”@paularambles- likes: 601
- replies: 2
- bookmarks: 33
- reposts: 24