4 ms·
The key was probably encoded in some way that made it hard to detect, for example, as a VM disk snapshot or a .tar.gz archive of a home directory. Something li
by sltkr 4y ago
The key was probably encoded in some way that made it hard to detect, for example, as a VM disk snapshot or a .tar.gz archive of a home directory.
Something like that must have happened anyway, since it's highly unlikely a private key is just lying around as a plain text file on an engineers workstation to be accidentally included in a push.
- buildbot 4y agoThat would make more sense, though cred scanning should at least attempt to unzip/untar compressed files IMO.