News for hackers. Stuff that matters.
Re:A practical guide to securing macOS by tptacek on Wednesday November 23, 2016 @02:50PM (#13025301)
I like reading guides like this, and they're useful in a sort of encyclopedic sense, but the problem with them is that they're really a "practical guide to doing every conceivable security thing you could do" with macOS, which is in fact not the best way to secure your operating system. For instance: it's probably not the world's greatest idea to go out of your way to install Adium for secure messaging on a locked-down Mac.

The cryptographic advice in this particular guide is not especially great. You can, for instance, safely ignore what it says about randomness (and, in particular, about how it interacts with FileVault's XTS block crypto). Its advice about password management is needlessly complex (if you trust Keychain, use Keychain Assistant to generate passwords, not OpenSSL --- but most of the cool kids just use 1Password, and they're right to do that).

Re:A practical guide to securing macOS by sanbor on Wednesday November 23, 2016 @09:53PM (#13027648)
I suggest pass [1]. It's just gpg with git. If you don't like the command line very much you can use a front end for desktop [2], Android [3] or iOS[4]. There are scripts to migrate from others password managers.

[1] https://www.passwordstore.org/

[2] https://qtpass.org/

[3] https://github.com/zeapo/Android-Password-Store/

[4] https://github.com/davidjb/pass-ios

Re:A practical guide to securing macOS by binaryapparatus on Thursday November 24, 2016 @05:18AM (#13029500)
I am using pass on Mac and all other computers for over a year. The only thing missing is proper dmenu alternative for Mac but I modified https://github.com/oNaiPs/dmenu-mac to work with pass and paste username/password to the clipboard. If I get time I will publish this code because it makes pass fly.
Re:A practical guide to securing macOS by JumpCrisscross on Wednesday November 23, 2016 @03:14PM (#13025489)
> most of the cool kids just use 1Password

Do you have a view on 1Password versus LastPass?

Re:A practical guide to securing macOS by reconbot on Wednesday November 23, 2016 @03:54PM (#13025767)
I do, I've been a heavy user of both for 4+ years, but I'm not a security expert of any kind.

LastPass has been exploited a few times in ways that could have given up passwords. Their UX and server infrastructure seems to be a mess of php scripts, that itself doesn't have to be insecure but is a code smell. Their commercial support looks unmaintained. Both platforms support "cloud" based syncing but since 1Password's is pretty new I can't speak to it.

1Password does local encryption outside of the browser, LastPass will encrypt locally in the browser.

1Password can leverage other file transports to sync passwords, iCloud, DropBox, or any shared directory. LastPass does it all with their servers.

LastPass's web interface if compromised can have you give away the password to all your passwords. 1Password has a much smaller risk of this and would probably have to include a malicious software update.

1Password Families/Teams exists and I'm not familiar with it but it probably has a similar attack vector to LastPass's web interfaces.

You know, they both offer end to end encryption with similar attacks. Overall these companies are big targets and I'd rather keep my passwords offline or synced via side channels in a standalone app like 1Password.

PS I'd be amiss if I didn't mention dashlane https://www.dashlane.com/ I hear good things and it's passed review at a few companies who know their stuff, but that's all I know.

Re:A practical guide to securing macOS by arthurfm on Wednesday November 23, 2016 @09:42PM (#13027598)
> I hear good things and it's passed review at a few companies who know their stuff

Tavis Ormandy found some really bad vulnerabilities in Dashlane (and 1Password). [1] [2] [3] [4]

[1] https://bugs.chromium.org/p/project-zero/issues/detail?id=89...

[2] https://twitter.com/taviso/status/769391927892598784

[3] https://twitter.com/taviso/status/763801055725359104

[4] https://twitter.com/taviso/status/773218040758448128

Re:A practical guide to securing macOS by tptacek on Thursday November 24, 2016 @12:25AM (#13028373)
So far as I know, he only found a vulnerability in the Windows version of 1Password, which is now fixed.

I don't know anything about Windows 1Password, but for macOS, I strongly recommend 1Password over any of the alternatives.

Re:A practical guide to securing macOS by milkytron on Wednesday November 23, 2016 @05:41PM (#13026385)
After reading this I deleted my lastpass account and came across this message upon trying to log in.

http://imgur.com/a/SFpWw

One of the first things I learned about security was not to tell the user which credential was incorrect.

Disclaimer: I'm not a security expert.

Re:A practical guide to securing macOS by jerf on Wednesday November 23, 2016 @09:36PM (#13027571)
The debate that the smart people have on that one still seems to go back and forth. I can find people I respect who have both opinions.

My only contribution is that I suspect that in practice almost every site leaks this info if you try hard enough, via some form of timing attack. You can get off-the-shelf "constant time string comparison" algorithms, but it's impractical to write anything much larger in a constant-time fashion, certainly nothing as complicated as a full authentication flow, especially in the light of the complexity of the systems we program on nowadays, with so many layers of caching to exploit for timing, etc. I've leaned in the direction of going for the user-friendly approach in my code, though I've only come around to that recently.

Re:A practical guide to securing macOS by emodendroket on Wednesday November 23, 2016 @08:32PM (#13027252)
I mean, honestly, it's not a crazy trade-off to let people see the username, especially if you have a registration page that's going to tell people "sorry, that name is already registered."
Re:A practical guide to securing macOS by welly on Wednesday November 23, 2016 @06:28PM (#13026663)
I've been using Dashlane for the past 12 months. It is excellent. Integrates well with OSX, Chrome, Firefox and Android, haven't heard of any security issues/break-ins or them handing out everyone's password data to anyone who shouldn't have them. I'm sticking with Dashlane for the foreseeable future. There's certain things that would be "nice to have" such as an API so a command line utility could be built but I'll deal with it.
Re:A practical guide to securing macOS by paws on Wednesday November 23, 2016 @03:51PM (#13025755)
A friend recently introduced me to Keepass[1], it seems to be an open source 1Password. I'd be interested in opinions on that, especially @tptacek's.

[1] http://keepass.info/

Re:A practical guide to securing macOS by SadWebDeveloper on Wednesday November 23, 2016 @04:24PM (#13025934)
You will probably get tons of bad comments on KeePass security (specially for 2.x the "Professional" version, since its developed with .NET C#) but KeePass threat model is way more easy to handle/secure than any of those cloud based password providers. Just remember to keep it updated and use password and key to protect your database. Plus remember to read the Security section for clarification on "ways to pwn you": http://keepass.info/help/base/security.html
Re:A practical guide to securing macOS by 9point6 on Thursday November 24, 2016 @07:25AM (#13029955)
KeePass has open source clients on every major platform.

A central cloud service using closed source applications for storing passwords just seems like an easy target for assailants.

Re:A practical guide to securing macOS by wglb on Wednesday November 23, 2016 @05:07PM (#13026159)
Friends don't let friends use LastPass.

Use 1Password.

Re:A practical guide to securing macOS by hackuser on Wednesday November 23, 2016 @05:54PM (#13026455)
why?
Re:A practical guide to securing macOS by welly on Wednesday November 23, 2016 @06:23PM (#13026629)
Friends don't let friends use 1Password.

Use Dashlane.

Re:A practical guide to securing macOS by matthewcford on Wednesday November 23, 2016 @07:12PM (#13026880)
for better sharing and groups - I prefer lastpass.
Re:A practical guide to securing macOS by tptacek on Wednesday November 23, 2016 @05:03PM (#13026133)
Yes: use 1Password.
Re:A practical guide to securing macOS by bigiain on Wednesday November 23, 2016 @08:21PM (#13027175)
I'm assuming this specifically refers to the 1Password app (iOS and macOS)? Do you have better-informed-than-me opinions of their web based 1Password for Teams? (I'm using it at work, but don't "trust" it in the way I trust my personal passwords to the 1Password apps on my phone and laptop. Not because I know of any specific vulnerabilities, but just because "Web app? surely that's a probably-unnecessary risk for my passwords?")
Re:A practical guide to securing macOS by pimeys on Wednesday November 23, 2016 @05:46PM (#13026407)
1Password doesn't seem to support Linux, so that's a big dealbreaker...
Re:A practical guide to securing macOS by kazazes on Wednesday November 23, 2016 @11:49PM (#13028202)
I've run 1Password in wine on Arch for years. Both the app and the browser plugin are styled like Win95 applications (even after changing the winecfg settings), but otherwise run flawlessly.

I have wondered if running 1Password through wine would introduce some not-considered attack vector, but I've yet to hear it.

Re:A practical guide to securing macOS by nzgrover on Wednesday November 23, 2016 @08:11PM (#13027123)
Re:A practical guide to securing macOS by specialist on Wednesday November 23, 2016 @05:39PM (#13026371)
This guide lost me (a noob) at "Create a threat model".

I don't even know what questions to ask. Much less choose the appropriate options.

And I'd have very different answers for my work and home gear.

Re:A practical guide to securing macOS by csydas on Thursday November 24, 2016 @01:41AM (#13028658)
I think you might be over thinking it, though I can understand how it's a daunting question.

I believe the intent is to ensure that it's understood the list isn't a requirement, but rather the varying options and levels of secure you can have based on your wants/needs.

When asking someone to create a threat model, you can begin with a simple question: "What are you afraid someone will do to your computer?" From this, you can then begin to piece through the list and look for items that address that.

Just care about malware? Look at the scanning tools.

Fearful that some bored teens in eastern europe are goofing around with hacking shit? Look at the security and notification tools

Think Putin is sending the new FSB/KGB after you for your exfiltrated борщ recipe? Look at the disk encryption section. (and perhaps professional help)

Maybe it could use some clarification, but I think the author's intent here was to convey that the list isn't a laundry list of "do this or your computer is going to be attacked", but more that you get what is required for your needs. Many of these tools require that you adopt different computing habits than traditional computing, and not all are applicable to every single use case.