News for hackers. Stuff that matters.
Re:FSF responds to Microsoft's privacy and encryption announ... by jevinskie on Thursday December 05, 2013 @04:08PM (#6857255)
It seems like the response glosses over what Microsoft is actually doing and instead just attacks them for something unrelated (Widows is closed source). In the FSF eyes, Microsoft can do nothing to improve security until Windows is open sourced.
Re:FSF responds to Microsoft's privacy and encryption announ... by obituary_latte on Thursday December 05, 2013 @04:16PM (#6857296)
No, I think in the FSF's eyes -- rightfully -- it can't be proven that security has improved.

I also can't agree that it isn't related. If I tell you I'm wearing a green shirt, how can you know for sure if you or someone you trust hasn't verified it? You can't. It's the same with MSFT. But in the case of MSFT, it has been proven that they wear a lot of Hypercolor[1] stuff.

Is it good that MSFT is doing stuff to make things more secure? Sure. Do we still have to take it on faith that they are doing everything they can to protect their users? Yup.

[1]http://en.wikipedia.org/wiki/Hypercolor

Re:FSF responds to Microsoft's privacy and encryption announ... by criley2 on Thursday December 05, 2013 @04:26PM (#6857379)
So, Microsoft and its Windows product adheres to no industry standards, has no external audit process, has never been verified by a private or Government contract agency through audit or other verification process?

I work in a small programming company and we do internal and external audits while maintaining compliancy with federal and state regulators as well as groups like ISO.

Sure, our work is closed source, but that doesn't automatically mean it hasn't been externally verified for a number of different things by a number of different organizations...

Re:FSF responds to Microsoft's privacy and encryption announ... by obituary_latte on Thursday December 05, 2013 @04:33PM (#6857421)
No, I did not say those things. That aside, if you wanted to, after an audit/review concluded, could you put a backdoor in your software? Since it's closed source, would anyone know about it?
Re:FSF responds to Microsoft's privacy and encryption announ... by andrewfong on Thursday December 05, 2013 @04:43PM (#6857488)
If there's a deterministic build process, in theory, the auditor would know something was up if the binary differed.
Re:FSF responds to Microsoft's privacy and encryption announ... by venomsnake on Thursday December 05, 2013 @04:42PM (#6857482)
In deterministic build? It will be very hard. I doubt that any audit signs on anything other than specific versions.
Re:FSF responds to Microsoft's privacy and encryption announ... by throwaway2048 on Thursday December 05, 2013 @04:58PM (#6857604)
does microsoft use deterministic builds?
Re:FSF responds to Microsoft's privacy and encryption announ... by riquito on Thursday December 05, 2013 @04:57PM (#6857590)
There are these things called signed binaries...
Re:FSF responds to Microsoft's privacy and encryption announ... by danbruc on Thursday December 05, 2013 @05:36PM (#6857889)
But signing binaries does not prove from which source the binaries have been build, only who did it.
Re:FSF responds to Microsoft's privacy and encryption announ... by rbanffy on Thursday December 05, 2013 @05:21PM (#6857777)
> Sure, our work is closed source, but that doesn't automatically mean it hasn't been externally verified for a number of different things by a number of different organizations...

Yes, but we have to take your word for it.

Re:FSF responds to Microsoft's privacy and encryption announ... by danbruc on Thursday December 05, 2013 @05:39PM (#6857916)
As mentioned below, a software being secure and the ability to convince yourself that a software is secure are two different things.
Re:FSF responds to Microsoft's privacy and encryption announ... by belorn on Thursday December 05, 2013 @06:12PM (#6858096)
Audit and verifying the security of software the size of Microsoft Windows without source code is like auditing and verifying the security of the international space station with only the help of a hand held telescope.

Sure, it looks like its not leaking air. It has not dropped down to earth yet, and all the videos posted on their website looks to show it being fine. However, if I ever went there and depended on its security, I would demand more.

Re:FSF responds to Microsoft's privacy and encryption announ... by the_af on Friday December 06, 2013 @07:07AM (#6860671)
If a piece of proprietary/close source software gets audited by an external agency, any of the private actors involved can be involved in deception (the authors of the software, the auditing company and the government or whatever). They can all be in collusion. This would have sounded like a conspiracy theory before recent discoveries, but now we've seen this can actually happen.

Whereas if the source is open, and you are a subject matter expert (yes, that's a big if), you can review the source yourself. You can decide for yourself whether the software has an NSA backdoor, an innocent flaw or whatever.

Yes, a lot of people, myself included, don't have the technical background to do this. But with open source we could, if we had the knowledge (which can be learned), without relying on potentially compromised authorities.

With closed source we simply can't. We have to trust the auditors and the government, which have been shown to be unreliable.

Re:FSF responds to Microsoft's privacy and encryption announ... by hansjorg on Thursday December 05, 2013 @04:16PM (#6857298)
Why would you place any amount of trust in a closed source privacy solution from a company with a history such as Microsoft's?
Re:FSF responds to Microsoft's privacy and encryption announ... by codezero on Thursday December 05, 2013 @04:26PM (#6857370)
Because they employ intelligent, skilled people who care and know more about privacy than I do.

How many open source projects have most people audited for their own sense of satisfaction about its security promises?

Re:FSF responds to Microsoft's privacy and encryption announ... by electic on Thursday December 05, 2013 @04:48PM (#6857516)
Unfortunately, those skilled people at MS have let the NSA in on so many 0-day exploits. God knows how many have not been reported to the public yet. At least with open source, I know there is a community behind it for me or others to verify. Sure it is not 100% fool proof, but it makes it far harder to sneak bad things through.
Re:FSF responds to Microsoft's privacy and encryption announ... by DanBC on Thursday December 05, 2013 @04:50PM (#6857535)
> Sure it is not 100% fool proof, but it makes it far harder to sneak bad things through.

Debian SSL bug lasted 2 years. Open source means little for security.

Re:FSF responds to Microsoft's privacy and encryption announ... by throwaway2048 on Thursday December 05, 2013 @05:04PM (#6857639)
cherrypicked examples mean little for arguements either. The WMF exploit was in windows for more than 15 years.

http://en.wikipedia.org/wiki/Windows_Metafile_vulnerability

Re:FSF responds to Microsoft's privacy and encryption announ... by DanBC on Thursday December 05, 2013 @05:07PM (#6857670)
SSL is a security sensitive bit of code. That's the kind of thing that needs to be kept safe, and it's the kind of thing that people claim is kept safe my open source's many eyes.

The argument I'm making is not that Windows is secure (because it isn't), but that Open Source isn't necessarily secure just because it's open source.

Re:FSF responds to Microsoft's privacy and encryption announ... by belorn on Thursday December 05, 2013 @06:19PM (#6858120)
No one has argued that open source is secure just because its open source.

Open source is however possible to independent verify if it is secure. Closed source is not possible to verify as secure and must be taken solely on the word of the company who made it.

Re:FSF responds to Microsoft's privacy and encryption announ... by kkangaroo on Thursday December 05, 2013 @05:54PM (#6858003)
There are a lot or security holes regularly surfacing in all kinds of software. We don't even have the post mortem of the kernel.org compromise , as one example. Even some Debian servers got hacked. Open source helps but lets not pretend it's a panacea.
Re:FSF responds to Microsoft's privacy and encryption announ... by the_af on Friday December 06, 2013 @06:57AM (#6860629)
It's not all or nothing. Open source is better than close source for security auditing purposes, but of course open source alone is not enough, nor is it impervious to security flaws. It's just better than the alternative.
Re:FSF responds to Microsoft's privacy and encryption announ... by rbanffy on Thursday December 05, 2013 @05:22PM (#6857788)
> Debian SSL bug lasted 2 years. Open source means little for security.

How many examples can you come up with? Was this specific bug being actively exploited when it was discovered?

Re:FSF responds to Microsoft's privacy and encryption announ... by DanBC on Thursday December 05, 2013 @05:37PM (#6857896)
> How many examples can you come up with?

A bug caused by prettying the code, which was secure from upstream, which is in an important, widely used, supposedly secure bit of code isn't a good enough example?

> Was this specific bug being actively exploited when it was discovered?

Many Linuxes used to ship with lots of services running. That lead to many rooted boxes being used to deliver spam. Open Source fixed the problem, but only after many millions of emails had been delivered.

Someone somewhere probably has a nice chart of all the Red Hat boxes in SKorea in the late 1990s early 2000s.

Again, this isn't to suggest that MS or Apple are more secure. For years anyone putting an MS server onto the Internet ran the risk of very quick exploitation.

Re:FSF responds to Microsoft's privacy and encryption announ... by rbanffy on Thursday December 05, 2013 @05:43PM (#6857939)
> A bug caused by prettying the code, which was secure from upstream, which is in an important, widely used, supposedly secure bit of code isn't a good enough example?

It's a good example. Can you come up with more? Because, you know, it's just one instance of a problem. It says nothing on how pervasive it is.

> For years anyone putting an MS server onto the Internet ran the risk of very quick exploitation.

IIRC, there was a time when the average time between install and first invasion was in the 40 seconds range.

Re:FSF responds to Microsoft's privacy and encryption announ... by the_af on Thursday December 05, 2013 @04:17PM (#6857311)
I think the article glosses over Microsoft's security measures by design. It is consistent with the FSF's position that closed/proprietary source is inherently more insecure than open source because you cannot freely review (even if you have the technical knowledge to do so) whatever measures the authors say they implemented.
Re:FSF responds to Microsoft's privacy and encryption announ... by strlen on Thursday December 05, 2013 @05:34PM (#6857869)
It is very much related: closed source software isn't audited in the open. Core principle of building secure software is one must assume that their adversary has the source code and is actively building newer and newer attacks based on it (corporate leaks happen all the time). It's not impossible to follow through with this principle when building closed source software, but it is a lot easier to handwave it.

I am not a fan of FSF's tone here, they could be more diplomatic -- but saying "we appreciate your effort, but you fail" would have been more insulting. I think there are many places for closed source software, but core privacy software is not one of those places.

The encryption core (the critical pieces that either input or output plain text -- the places where the attack is more likely to succeed as opposed to the core of the algorithms), as well and the general platform should have the source code available (even if at a fee). That's not quite the FSF vision, but perhaps the powerful vision is needed (one can think of FSF's goals as a captivating utopian story that leads to more incremental improvements).