3 ms·
> So you can do a code review on the entire Linux codebase and you are skilled enough to find any security vulnerability? My odds there are much better than th
by lisper 9y ago
> So you can do a code review on the entire Linux codebase and you are skilled enough to find any security vulnerability?
My odds there are much better than they are trying to do a similar audit on MacOS.
> Can the person you hire do it?
There are people out there who are extraordinarily skilled at this sort of thing. Security flaws in, say, iOS are found regularly. That's how jailbreaks work. (And, BTW, the fact that Apple doesn't give me the option of opening up the jail on my own phone means that if I want this freedom I have no choice but to run some black-box binary from some unknown Chinese hackers. That is by far the biggest security risk I face when using Apple products and it is a direct result of their policies.)
> Would they have found the Heartbleed issue that was in open source code for at least two years?
They did find it, and I didn't even have to pay them. If I had paid someone to look, they might have found it sooner.
No system will ever be perfect. But I like my odds on Linux much better than on Apple.
- scarface74 9y agoMy odds there are much better than they are trying to do a similar audit on MacOS. Based on what metrics? Someone skilled in Assembly can and has found many vulnerabilities in closed source software. The chance of you as an individual being able to audit the entire Linux codebase and finding a new vulnerability are nil unless you have some special skills that you haven't mentioned that make you better than some of the top hackers and researchers. There are people out there who are extraordinarily skilled at this sort of thing. Security flaws in, say, iOS are found regularly. Despite the fact that is closed. How does that support your point that "open" software is easier to find vulnerabilities. You said that you could hire someone to audit the code, could you afford them? That's how jailbreaks work Without the code being open... (And, BTW, the fact that Apple doesn't give me the option of opening up the jail on my own phone means that if I want this freedom I have no choice but to run some black-box binary from some unknown Chinese hackers. That is by far the biggest security risk I face when using Apple products and it is a direct result of their policies.) Apple has the source code for all of the chips they use and they had a hand in designing most of them. As opposed to the random Android manufacturer who outsources their chips and the manufacturers give the OEMs binary blob drivers. Even Google said they couldn't upgrade one of their devices because they couldn't get drivers for one of their chips. Do you really run your Android phone with all open source software that you compiled and installed yourself? Including the various drivers? Have you audited all of it? They did find it, and I didn't even have to pay them. If I had paid someone to look, they might have found it sooner. And they've also found bugs in close Software and if you pay someone enough they could find stuff too. No system will ever be perfect. But I like my odds on Linux much better than on Apple. Based on what objective metrics?
- nightski 9y agoWhy do you keep insisting it comes down to him to audit the entire Linux codebase? The advantage of it being open is that there are millions of potential eyeballs out there all with different areas and levels of expertise.
- 15155 9y agoThis is a super important point. A complete layperson can use open-source software knowing that it has been looked at by at least some part of the community, conferring all kinds of security benefits.
- scarface74 9y agoAnd that same lay person can assume some experts (including some at Google) have looked at closed source software. But all of the people running Linux on x86 had no way of knowing that there was a bug in the x86 microcode.
- secstate 9y agoThese are all terrible arguments, sir. There is absolutely no way to make an argument that closed-source software is just as auditable or secure as open-source software. There will always be methods of trust required when you use things other people made, but when software is developed in a black box, with NDAs you didn't know existed, or 0-days known about for years, you simply CANNOT make an analogy to heartbleed. Heartbleed was one vulnerably in a poorly maintained OSS library. It is foolish to use it as your primary example of the failure of OSS security when there are tens of thousands of closed tickets on Github, Bitbucket and Gitlab to that would argue OSS is easier to audit and easier to openly discuss ihfosec issues. By coming up with the same examples over and over again in lower threads you are coming close to trolling this thread and ought to stop and come up with a better argument for why a corporate system-on-a-chip system is inherently just as safe as hardware developed with open source firmware.
- 9y ago