It is my opinion that the following discussion
was terminated thru intervention via “abortion”, to use a figurative description of what I perceived happened.
There are VERY valid reasons for newcomers approaching the world of Linux wanting to have independant assurance of a “known” level of quality, as provided by an unafilliated 3rd-party.
The very “hands-off” approach of highlighting that Ubuntu and other OSS applications and OSs are indeed “Open-Source”, allowing for anyone to review the code, does not address the inherent need which stems from the fact that many (dare I say most) of those who are considering to move away from Windows (or other systems) simply lack the competence due to lack of awareness, skills, tools, or reputation required to make the kind of assessments/determination that could lead them perform the type of Certification being discussed themselves.
To ignore that reality is, in my view, disrespecting the people who make up the marketplace from which the OSS Community hope to attract those adoptees.
Let us not lose sight of the fact that people can and do recognize acts of disrespect, intentional or not, and distance themselves from those who intentionally or unwittingly offer such disrespect.
Given the context the above attempts to clarify, I respectfully ask the powers that be … that the request … put forward by @SleepTimer … be reconsidered, possibly in the form of a more “focused” goal, of limiting such an audit to the elements that compose the “installed default” configuration, for any of the Flavours.
Now, I understand that there are many Distros that make use of some of the same building blocks for the OS/Distros.
Yes, it would be difficult to get everyone on-board to insist on seeing some documented evidence of process control for each of those shared components, but for some of those key components, like the Kernel, couldn’t the industry come together to “encourage” the upstream provider organization to accept such an audit, as a means to give the eco-system a greater visibility of “discipline” and “accountability”?
Maybe an “ISO Certification” would address that market need.
I do know, given the eco-system, that it would be near impossible to obtain Common Criteria certification for every little bit of the eco-system, but would it be completely unreasonable to have some expectation, for a default installation of Ubuntu (any flavour?), that it be Certified for
and that the installation-time interraction allows the choice of applying that Certified installation … or “scaling back” to the current default installation configuration which, correct me if I’m wrong, does not comply with that “minimum” benchmark.
Yes, I do realize that I have crossed the boundary from “Quality” in to the realm of “Security”. But truly, isn’t that what everyone’s real focus is these days?
After all, being able to reassure both the General Public, or Business Decision-Makers, that various configurations actually conform to, and assure, various “established” Protection Profiles for targetted scenarios, would go a very long way towards regaining Public trust in informatics and network infrastructure that has been steadily undermined with each new instance of breach, let alone tampering, that is reported in the news.
I respectfully submit the above for consideration.