Live data from Hacker News

~/.osx updated — sensible hacker defaults for OS X Mountain Lion

github.com

41–50 of 91 posts

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#41
post #25
post #7

This isn't "sensible hacker defaults", it's more like "some guy's view of what Mac OS X should be like".

Unilaterally resetting the scroll direction to the 10.6 standard is insanely presumptuous.

So was unilaterally setting it to the 10.7 standard. I think we should have the script flip a coin so people are annoyed evenly.

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#42
post #37

defaults write com.apple.LaunchServices LSQuarantine -bool false This is a terrible idea. If your browser, or anything else, is ever conned into downloading and opening a file, the quarantine is the difference between "what the fuck, why is an executable I've never launched before trying to launch?" and silently getting owned.

Sorry - this is total security theater. I download almost everything from the net - how else would I install? CD? Floppy? Telling me that it's downloaded from the internet doesn't do anything to identify that it's dangerous and so I ignore the warning. Under what circumstance would I go "whoa, maybe it's dangerous this time"??? Mac's don't have auto-install .exe files. Yet we get warning for everything from JPEGs to…

If you can execute code, said code could be an auto-installer.

If there's a vulnerability in the application used to open a JPEG or whatever, you can execute code.

It's less asking "is this dangerous?" and more "did you download and open this?"

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#43
post #37

defaults write com.apple.LaunchServices LSQuarantine -bool false This is a terrible idea. If your browser, or anything else, is ever conned into downloading and opening a file, the quarantine is the difference between "what the fuck, why is an executable I've never launched before trying to launch?" and silently getting owned.

Sorry - this is total security theater. I download almost everything from the net - how else would I install? CD? Floppy? Telling me that it's downloaded from the internet doesn't do anything to identify that it's dangerous and so I ignore the warning. Under what circumstance would I go "whoa, maybe it's dangerous this time"??? Mac's don't have auto-install .exe files. Yet we get warning for everything from JPEGs to…

In principle, you shouldn't be getting warnings for any of those formats. You should only be getting one when you launch an executable - it's a warning that the file you downloaded is an executable and not some random other file you can (barring vulnerabilities) open without trust.

I don't know why it cares about the executable bit(?) in this case, though.

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#44
post #42
post #37

Earlier quoted context omitted.

Sorry - this is total security theater. I download almost everything from the net - how else would I install? CD? Floppy? Telling me that it's downloaded from the internet doesn't do anything to identify that it's dangerous and so I ignore the warning. Under what circumstance would I go "whoa, maybe it's dangerous this time"??? Mac's don't have auto-install .exe files. Yet we get warning for everything from JPEGs to…

If you can execute code, said code could be an auto-installer. If there's a vulnerability in the application used to open a JPEG or whatever, you can execute code. It's less asking "is this dangerous?" and more "did you download and open this?"

If something else downloaded and opened the file, it's already owned your account, hasn't it? The horses are out of the barn at that point, right?

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#45
post #44
post #42

Earlier quoted context omitted.

If you can execute code, said code could be an auto-installer. If there's a vulnerability in the application used to open a JPEG or whatever, you can execute code. It's less asking "is this dangerous?" and more "did you download and open this?"

If something else downloaded and opened the file, it's already owned your account, hasn't it? The horses are out of the barn at that point, right?

There are 3 steps needed to exploit this attack vector (assuming no wetware exploits):

1. Download the file. Any website can do this by design.

2. Get LaunchServices to open the file. This requires at least one vulnerability.

3. Bypass quarantine. This requires at least one additional vulnerability.

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#46
Great list. Stripping animations out is always appreciated.

Does anyone know how to alter / remove the animation from horizontal motion between spaces? Particularly when using the keyboard shortcuts, this whizzing is disorienting and irritating.

I assume it is not possible, given that animation seems to be keenly bound to the trackpad 'peeking' operation and all.

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#47
post #4

As with any dotfile repo, I wouldn't recommend installing the entire thing at once. Instead, try and take the time to read through it and select settings that you want piecemeal. You'll end up knowing what everything does, especially in the case that something strange happens and you want to tweak things. Edit: I should note that I learned this the hard way starting out, I went backwards by ripping out things that di…

As the author of this dotfiles repository, I completely agree. These are my settings, and I’m sure not everyone will like this configuration. The idea is that automating all these OS X preferences (hidden or not) can save you a lot of time if you need to set up new accounts for yourself on a regular basis.

TL;DR This repository is meant to be forked, not used as-is.

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#48

Earlier quoted context omitted.

That's not buggy, that's a text file with it's executable bit set, which is actually potentially dangerous.

Under what scenario is it ever unsafe to open a text document in TextEdit? Under what scenario would you ever not completely ignore that warning? A much more likely threat is a malformed jpg or pdf designed to exploit a decoder, in which case the executable bit is completely irrelevant. Warning the user about the executable bit protects them from nothing, unless Finder is preparing to execute the file itself. It is a…

TextEdit could have a bug in its 'guess the character encoding' code that leads to a buffer overflow, or it could have a bug handling malformed UTF-8.

Its 'guess the character encoding' code also might have a 'wait a minute, this is RTF/PDF' feature.

Of course, Apple could trust its own apps, but I think they should not (why increase the attack surface?) and that would lead to complaints "why can't I tell this OS that my text editor can be trusted?".

I also think (but have no data on it) that this "open a .txt file you downloaded" check is very rare for 'normal' users. If they download at all, it is Word documents, PDFs, movies, and applications.

Re: ~/.osx updated — sensible hacker defaults for OS X Mountain Lion

#49
post #25
post #7

This isn't "sensible hacker defaults", it's more like "some guy's view of what Mac OS X should be like".

Unilaterally resetting the scroll direction to the 10.6 standard is insanely presumptuous.

I much prefer natural scrolling, but the 10.6 standard has the same thing going for it as vim: it works everywhere. I gave up trying to reverse the scrolling in Windows with AutoHotkey, it was a mess. :(
Post reply on HN