> If the concern is leaks, defense contractors like Galois might be able to get DARPA to change that policy. I don't think any one thing at either the DARPA or

> If the concern is leaks, defense contractors like Galois might be able to get DARPA to change that policy. I don't think any one thing at either the DARPA or Galois level can change this policy. It's a question of whether or not you are doing fundamental research, i.e. are you a 6.1, 6.2 or 6.3 program. If you want to do fundamental research on an applied research contract, you're going to have a bad time. > Anyone with DARPA or Defense experience think this proposal has a good chance of working? Frankly, no. This is a technical solution to a problem that is much deeper. How does having a compartmented mode workstation help with this problem? Let's say that there's the main fork A and the private fork B. Someone comes up with a sensitive change to B that is, I dunno, about 50 lines. Someone else working on both A and B sees this change to B and they think oh hey, I could do something similar in A, so they write, from scratch, a similar change and commit it to A. They do this without having any file cross any isolation boundary, they just type stuff with their fingers.