News for hackers. Stuff that matters.
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.