News for hackers. Stuff that matters.
Re:The VeraCrypt Audit Results by FieryTransition on Monday October 17, 2016 @06:23PM (#12730350)
Valid points, though I would consider the requirements for writing really secure software quite high, so I do not think most open source projects could meet such standards. Maybe it could be compared to developing mission critical software, like Nasa for example. The amount of resources and rigor they use to get bugs out of the code is out of the scope of most free/donation software projects. There are probably a few open source projects which gets close to being considered secure though, mostly those which are very used and backed by big companies or foundations.

So we have Veracrypt as the 'good enough' option right now and ease of use, but you shouldn't happen to know any secure alternatives? You seem to know a bit about this.

Re:The VeraCrypt Audit Results by nickpsecurity on Monday October 17, 2016 @09:10PM (#12731233)
"though I would consider the requirements for writing really secure software quite high, so I do not think most open source projects could meet such standards. "

Data from prior work indicates it ranges considerably from significantly harder to extremely hard. The LOCK system with an Orange Book A1 development process was highly secure and gave cost breakdown. A1 assurance acyivities added around 37% or so on top of regular, labor cost. Altran/Praxis's Correct-by-Construction that does highly-assured systems with mix of Z specs, Ada, SPARK, reviews, and testing costs 50% premium on top of normal development. Just using SPARK automatically knocks out whole classes of bugs. Galois did and open-sourced CRYPTOL so people can specify algorithms in easy DSL then generate C from it. Also parser and protocol generators.

So, prior evidence shows it takes specialized skill and domain knowledge... at least two extra people unless one has both... but otherwise costs 30-50% more time. Like Cleanroom methodology, it partly achieved this by saving you time debugging and refactoring due to reduced bugs in general plus doing fixes earlier in lifecycle.

Most OSS projects dont do this stuff just because they dont know it's necessary, don't care, or don't have staff for both demanded features and assurance activities. Interestingly, there's more high-assurance products in proprietary than FOSS software despite the huge labor advantage FOSS has. That there's little of even medium-assurance work in majority of both says even worse things about IT's priorities or apathy given medium assurance cost little to nothing. Microsoft is the one exception of big, software houses via SDL and MS Research's work. For FOSS, DJB, OpenBSD, and SQLite come to mind.

Re:The VeraCrypt Audit Results by FieryTransition on Tuesday October 18, 2016 @11:18AM (#12735290)
Thanks for the info, did some searching based on your comment and I managed to find a report made by Altran/Praxis detailing the development process and technologies for a tokeneer ID station implementation they did for the NSA. Very interesting stuff. http://www.adacore.com/uploads/downloads/Tokeneer_Report.pdf

It really shows the amount of resources and knowledge required for actually having safe or secure systems.

Re:The VeraCrypt Audit Results by nickpsecurity on Tuesday October 18, 2016 @12:35PM (#12736142)
Glad you enjoyed it. Remember Praxis' method next time some fool says you can't engineer software. A few companies like them do. They're now just called Altran. The Tokeneer link was good since they published the source code on AdaCore website for people to learn from. However, the highest-security thing they did was the CA below under UK equivalent of EAL6/7. http://www.anthonyhall.org/c_by_c_secure_system.pdf

Example of new one for model-to-code-to-ASM verification https://www.umsec.umn.edu/sites/www.umsec.umn.edu/files/hard...

LOCK project was pretty landmark in all that it accomplished with Sidewinder firewall & SELinux being in its ripple effects http://www.cyberdefenseagency.com/publications/LOCK-An_Histo...

The B method is one of most successful in industry. You'll definitely see the engineering aspect in this one. http://www.methode-b.com/wp-content/uploads/sites/7/2012/08/...

Cleanroom was early one in 1980's (start at p13) https://www.sei.cmu.edu/reports/96tr022.pdf

Note: Cleanroom had excellent results at low cost but disappeared for some reason. I saw someone recently combine Python with Cleanroom with good results. Cleanroom's compositional style means something like Haskell + QuickCheck could be great combo. If anyone tries it, let me know about the results.

Re:The VeraCrypt Audit Results by JoachimSchipper on Tuesday October 18, 2016 @03:52AM (#12732795)
Really secure software isn't easy to write. But we're not holding the VeraCrypt developers to a higher bar than the one they've set for themselves.

For disk encryption, use whatever comes with your system. If you have no preference, Microsoft's BitLocker is excellent - it can incorporate hardware security features such as a TPM, self-encrypting (OPAL) SSD, it's somewhat easy to administer, etc.

Re:The VeraCrypt Audit Results by GordonS on Tuesday October 18, 2016 @06:18AM (#12733237)
If you are on Windows 10, the Home edition doesn't come with BitLocker - so your choice is to upgrade to Pro or use something else, such as VeraCrypt.

I think it's probable that both can be broken/bypassed by state actors - I'd be happy to use either as a defence against everyone else though.

Re:The VeraCrypt Audit Results by krylon on Tuesday October 18, 2016 @07:55AM (#12733583)
> For disk encryption, use whatever comes with your system.

I acknowledge this is likely a super-niche problem, but if you want to use an encrypted thumb drive (or external HDD/SDD) to access data from Windows, Mac and Linux machines, there is almost no alternative. Is there any realistic alternative?

And BitLocker, even if you are on Windows is not completely trouble-free - on Windows 7, e.g. to my knowledge only the Ultimate/Enterprise editions support it. Windows 7 Pro does not.

Re:The VeraCrypt Audit Results by acqq on Tuesday October 18, 2016 @10:16AM (#12734518)
Regarding BitLocker, even on Windows 10 Pro, you can't encrypt the virtual disk and put it on the DVD or BlyRay and later read from there directly (why? because MSFT). That means it's not suitable at all for longer-term archiving.
Re:The VeraCrypt Audit Results by pjc50 on Tuesday October 18, 2016 @04:50AM (#12732967)
Bitlocker is excellent in a commercial environment, but the question some people are concerned about is how it might handle state-level threats. Although I suspect after Windows 10 techies would find that consideration moot, there are quite a lot of human rights people still using it for the usual reasons.
Re:The VeraCrypt Audit Results by hannob on Tuesday October 18, 2016 @06:16AM (#12733229)
If your threat model is that you assume your OS vendor is part of the attack then you can't use a proprietary OS.

There's probably no free OS either that can give you the confidence level you'd want, because you probably would want to have reproducible builds, a trustworthy update process (preferably with some kind of transparency log), a wide array of exploit mitigations (aslr/pie/pic, grsec kernel, maybe CFI). There's currently no free OS offering all of those.

Re:The VeraCrypt Audit Results by keithpeter on Tuesday October 18, 2016 @07:59AM (#12733597)
Just out of interest: is there any OS that offers all of those? Libre/Open Source/Free or proprietary (latter with source access I assume)?
Re:The VeraCrypt Audit Results by JoachimSchipper on Tuesday October 18, 2016 @05:41AM (#12733093)
If BitLocker seems riskier to you than VeraCrypt, might I suggest you recalibrate your threat model? See e.g. https://news.ycombinator.com/item?id=8193364.
Re:The VeraCrypt Audit Results by Cthulhu_ on Tuesday October 18, 2016 @06:33AM (#12733292)
Open source or not shouldn't be a constraint for spending resources and effort on code; it'd just mean development would be a bit slower and more tedious. But we're dealing with encryption here; if there's anything that should be done slowly, tediously and with an enormous amount of OCD, it's encryption software.