Re:Fully Countering Trusting Trust Through Diverse Double-Co...
by jacques_chester on Sunday October 09, 2016 @09:47AM
(#12671157)
Could you elaborate?
I get the sense that you feel it was always possible if upstream developers took the time and effort.
Which strikes me as a quite different approach to snapshotting filesystem layers.
Re:Fully Countering Trusting Trust Through Diverse Double-Co...
by ChoHag on Sunday October 09, 2016 @12:20PM
(#12671839)
The chance of an invisible magic snaphotting system not invisibly breaking the 'back-to-basics' assumptions is precisely zero, invalidating any tests performed within or by it.
Developing against a known state and always and only testing against that state is easy and has been since approximately always. Not doing it is lazy. Stop guessing, developers, programme!
Re:Fully Countering Trusting Trust Through Diverse Double-Co...
by jacques_chester on Sunday October 09, 2016 @12:29PM
(#12671882)
Could you give me some concrete examples so I can correctly understand you?
You may safely assume nearly-total ignorance on my part.
Re:Fully Countering Trusting Trust Through Diverse Double-Co...
by ChoHag on Sunday October 09, 2016 @12:42PM
(#12671958)
Concrete examples of what?
And ignorance of what? I don't plan to teach you programming here and now.
Re:Fully Countering Trusting Trust Through Diverse Double-Co...
by jacques_chester on Sunday October 09, 2016 @01:58PM
(#12672373)
You say containers are unnecessary because the problems have been solved.
What problems?
How are they solved?
I'm asking because I'm genuinely interested in understanding what you are trying to say.
Maybe I already know it. Maybe I don't. Right now I have no way to tell.
Docker wants to find the flaws on its own, so is repeating the last ~30 years of software distribution development.
Every problem containerisation discovers has been discovered. Every flaw it fixes has been fixed. All that is achieved by the modern insistence that containerisation is in any way something new is a larger attack surface. The ability to return to "some fixed point" has always been present and simple. Judging by many years of building other people's software, for fun or profit, developers simply don't bother to do so. None of my work is ever release without returning the system to a known state in order to run the necessary barrage of tests (which, developers take note, includes TESTING THE GOD-DAMN INSTALLATION DOCUMENT) and I've achieved this without the need for chroot, whatever its name du juor.
/rant