4 ms·
Even with this, people are dumb. It's probably not a case of "we didn't realize we were publishing to" and instead a case of "some dev didn't realize this was a
by landr0id 8y ago
Even with this, people are dumb. It's probably not a case of "we didn't realize we were publishing to" and instead a case of "some dev didn't realize this was a bad idea".
- pbhjpbhj 8y ago>some dev didn't realize Surely in a bank, when publishing, the decisions aren't down to a single dev. Either many people made a mistake together or many people made lots of small mistakes separately that added up to one big one?? FWIW, I don't know, I'm a small time potter, just how I imagine things happen in banks (I do know a couple of devs who work/worked for banks).
- jjeaff 8y agoYou are going to have a ton of technical barriers in place if you are going to stop everyone from publishing to one of the many and varied code repos out there.
- burfog 8y agoAn air gap will stop innocent mistakes and outsiders.
- smackfu 8y agoAnd kill dev productivity.
- burfog 8y agoNone of that productivity matters if the company dies due to being hacked into. You might not even know that this happened. Mysteriously, a clone company pops up, or a competitor seems to know all your contract negotiations and customers. Another possibility is that a lawsuit over data leakage takes out the company. Sometimes reputation alone can kill a company. BTW, it's really pessimistic to suggest that an air gap would kill productivity. It isn't that hard to physically transfer files from the computer at your left to the computer at your right. The disconnected network can have copies of popular software repositories, including for your OS to get updates.
- tracker1 8y agoIf your systems are so weak that seeing code puts you at risk, you have other issues.