Re:Remote Prompt Injection in Gitlab Duo Leads to Source Cod...
by mdaniel on Monday May 26, 2025 @05:20PM
(#44101795)
You're mistaking "know" with "care," since my experience has been that people know way more than they care
And I'm pretty certain that private repos are exempt from the platform's built-in secret scanners because they, too, erroneously think no one can read them without an invitation. Turns out Duo was apparently just silently invited to every repo : - \
Re:Remote Prompt Injection in Gitlab Duo Leads to Source Cod...
by tough on Monday May 26, 2025 @06:14PM
(#44102166)
I also remember reading about how due to how the git backend works your private git repos branches could get exposed to the public, so yea don't treat a repository as a private password mananger
good point the scanner doesnt work on private repos =(
Antoher interesting fact is that most big vendors pay for gh to scan for leaked secrets and auto-revoke them if a public repo contains any (regex string matches sk-xxx <- its a stripe key
thats one of the reasons why vendors use unique greppable starts of api keys with their ID.name on it