5 ms·
https://www.tesla.com/.gitignore https://www.tesla.com/.gitignore
by throwaway292939 4y ago
https://www.tesla.com/.gitignore https://www.tesla.com/.gitignore
- Alupis 4y agoEh, that was posted in another thread. It's really benign, and doesn't leak anything other than Tesla's website is a Drupal site... which was already known and easy to discover without the "leak". I would not say these "leaks" are necessarily incompetence like some have been quick to assume. These "leaks" don't really leak anything at all... and it's possible their team reviewed the files and determined "who cares". It's also pretty likely Tesla's staff has very little to do with the website, other than content. It's a Drupal site after all - some 3rd party might be in charge of hosting it, making this mistake theirs to own.
- sgammon 4y agoleaking info about your site / app is only benign until a motivated attacker finds and exploits it aside from being a potential security risk, it is downright embarrassing and sloppy, especially for a multi-billion $ company with a leader who is super vocal about "hard-core coding" musk fan or not that's pretty ironic
- Alupis 4y agoWell, nobody is "coding" a Drupal site. It's a CMS... and it's probably hosted by some 3rd party like these typically are.
- sgammon 4y agoso what? defacing their site and announcing fake news would still impact their stock price as shown re/twitter and Eli Lilly this month
- Alupis 4y agoThere's nothing in these "leaks" that are even remotely exploitable...
- sgammon 4y agothat we know of, at this time, sure. something isn't exploitable until you find an exploit, and then it's exploitable. knowing file paths for key configs on disk can't possibly help that equation.
- Alupis 4y agoBut like previously said, these are not secret paths. Everyone knows they are running a Drupal CMS, and those paths are baked into all Drupal sites. Literally nothing learned from these "leaks" that wasn't already known.