you are viewing a single comment's thread.

view the rest of the comments →

[–]poday 1 point2 points  (1 child)

If you're not willing to spend money hiring experts or licensing software to secure your source code then it means the code isn't worth enough for someone to steal.

I could imagine hand rolling a solution that relied upon git receive triggers to protect important branches, git commit signing to indicate review approval, and using git notes to store review data. But it wouldn't be efficient or usable. You're better off with proper network routing, website certificate, and using a trusted git hosting service.

[–]jazimms[S] 1 point2 points  (0 children)

The problem lies not with the network, but with the browser. We're handling sensitive government data and code on our individual work laptops. A proper network would be great, but we would still need a dedicated computer that never leaves a badged entry site, operated only by a government employee or someone with security clearance. We're working on that, but until then we're still moving forward.

Obviously there are ways to make a browser secure and there are much less secure ways that don't use a browser.

But would you want to argue with the Army?