Earlier quoted context omitted.
Which was caused in part by badly behaving programs (writing user data to the Program Files directory) that triggered the UAC prompt, if I'm not mistaken.
They improved the system in the next release, and since Win7 UAC generally works perfectly even with the "badly behaving" software. Sensitive directories are now mirrored elsewhere in the filesystem, so that when your program wants to read from, say, Program Files directly, what it really reads is C:/Users/[username]/AppData/Local/VirtualStore/...
Microsoft, Once Infested with Security Flaws, Does an About-Face
151–160 of 185 posts
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#152Earlier quoted context omitted.
Apple has always been exceptional in this regard as well. It usually drives people up a wall when this is pointed out, as the fanboys like to trumpet it a bit too loudly, but it's true. In-the-wild exploits are rare, and the company moves quickly to squash them and to prevent the entire category of exploit from biting them a second time.
There are a lot of great people at Apple and the security model of iOS is an achievement --- in a lot of practical ways better than that of Android. But I do not know a lot of people who would argue the Apple has a better security program than Google does. Google's team is better funded and better staffed, and has a much broader charter than Apple's.
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#153Earlier quoted context omitted.
I don't know. My father-in-laws Windows PC is routinely bogged down with malware/adware. It's not the same kind of security holes that used to be rampant, but it's still too easy for malicious software to cause trouble.
Though Microsoft have improved their computers still often come laden with crapware much of the time unlike Apple or I think most Chromebooks. You then end up with stuff like Superfish if you're not lucky.
Any system that allows free reign to OEMs will be ridlled with crapware.
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#154Earlier quoted context omitted.
Which was caused in part by badly behaving programs (writing user data to the Program Files directory) that triggered the UAC prompt, if I'm not mistaken.
They improved the system in the next release, and since Win7 UAC generally works perfectly even with the "badly behaving" software. Sensitive directories are now mirrored elsewhere in the filesystem, so that when your program wants to read from, say, Program Files directly, what it really reads is C:/Users/[username]/AppData/Local/VirtualStore/...
In my particular legacy-apps' field, I believe most problems are due to interactions with the DCOM subsystem though.
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#155Earlier quoted context omitted.
They improved the system in the next release, and since Win7 UAC generally works perfectly even with the "badly behaving" software. Sensitive directories are now mirrored elsewhere in the filesystem, so that when your program wants to read from, say, Program Files directly, what it really reads is C:/Users/[username]/AppData/Local/VirtualStore/...
So that 's what the policy "Virtualize file and registry write failures to per-user locations" does... uh, good to know :) thanks! In my particular legacy-apps' field, I believe most problems are due to interactions with the DCOM subsystem though.
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#156Earlier quoted context omitted.
Android's system security design is inferior to that of iOS. But, iOS's superiority (a) derives in significant part from Apple's total control over the hardware platform†, and (b) comes at the cost of a lot of user control tradeoffs that nerds like us tend to hate. Really, to suggest that Android's security is at parity with Apple's, you'd have to be arguing that Apple does a terrible job at exploiting their inherent…
On the other hand, I'm unaware of any automated analysis of applications on the iTunes App Store, dynamic or static. Doing this properly isn't in Apple's DNA. For example, when XcodeGhost apps infected some hundreds of millions of users, it took Apple days to take down the affected apps, seemingly waiting for third party reports instead of simply scanning the entire store for the XcodeGhost signature themselves.
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#157Earlier quoted context omitted.
> How are you ever going to assess the quality of this software in terms of security? If it's very important to you, you can obtain a license that includes source code: https://www.microsoft.com/en-us/sharedsource/
Or I could just use an open source alternative that does not require jumping through such hoops. One where I can edit and compile the source, run it and redistribute it, too. All for free. But I guess all that is also possible under this shared source program you mention?
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#158Earlier quoted context omitted.
If you like small code, simplicity, and a code-audit culture, look no further than OpenBSD.
A well-deserved endorsement from a Microsoft employee. (Assuming your HN profile is up-to-date.) The kernel I start with is indeed derived from the same one that project started with.
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#159Not sure 10 years is an about face?
Re: Microsoft, Once Infested with Security Flaws, Does an About-Face
#160Earlier quoted context omitted.
Perhaps you could explain how the statement "All software is large" "furthers the conversation"? How am I supposed to respond to that? You think that false statement is a respectable "response" to a comment on the benefits of small software? Small software exists both in the past (when memory and storage were more limited) and in the present. The very idea of small programs is a foundational one in the field of compu…
The point is small software just does less; when you need to do more you either build large software or you put together a bunch of small software which is effectively, from a security standpoint, the same thing. Small programs that don't do anything are secure but nobody cares. And you've probably written software larger than Notepad; a very popular small Microsoft program.
The only points I would contest are 1. that "a bunch" is effectively the "same thing" as large software. A "bunch" can vary in number and quality. My userland is a single "multi-call" binary and quite small. The sum total of source code is not so large that I cannot manage it. It's keeping tabs on the kernel code that presents the challenge; and 2. that "nobody cares".
If "nobody" cared, then you would not be seeing a comment such as mine because there would be nobody to author it.
Moreover there would be no reasonably small kernel source that users like me could use. Some people care enough to maintain that kernel and to keep it relatively small.
Maybe that group of people is like the software: small. Suits me just fine.