Live data from Hacker News

Do Not Type "File:///" in OS X

openradar.appspot.com

171–180 of 206 posts

Re: Do Not Type "File:///" in OS X

#171

Earlier quoted context omitted.

The fun thing about having it in messages.app, is it is actually a bug on the RECEIVING end of messages.app. And I can't seem to delete the message before the app crashes again. I'm so happy I have nice friends.

Disable your spell checker and it will stop crashing. Then you can delete the message, and re-enable the spell checker.

This did not fix it for me. Turned off spell checker and text substitution. Have another solution?

Re: Do Not Type "File:///" in OS X

#172
post #106

Hilarious. I pranked my friend with this, and now he's pissed. Oh well, it was certainly worth it. Interesting, though, what exactly causes this bug. It seems as if the built-in spellcheck seems to misinterpret the string "file:///" as some sort of alien construct, or perhaps false typed directories trigger some sort of lockdown. Either way, it's very puzzling how this sort of thing made it past the OS X developers,…

Doesn't Apple's quality control only apply to hardware? I hear people complain about bugs and just shear ugliness of their software pretty often.

Up until 10.6, actually, Apple used to produce very good, generally bug-free software. Starting with 10.7, they've begun to rush their software just because they have, say, 4 new "features". The yearly release cycle is partly to blame, but even then, iOS bugs are much more minor.

Re: Do Not Type "File:///" in OS X

#175
post #136

Earlier quoted context omitted.

checkDataDetectors will extract 'File://a/' - or any other 'complete' file URL - which at a minimum is a schema (file://) and a path '/' - as a valid data URL and then pass it to DDResultCopyExtractURL, which does some additional sanity checking. There it validates it by asserting that the URL begins with 'file://', which it doesn't. It then converts to an NSInternalInconsistencyException which is what crashes the ap…

Can you clarify what about that output shows that the crash cannot be exploited? Not doubting, just curious.

Unhandled exceptions can't be exploited in general, because they safely unwind the stack and terminate the application. This crash is just an unhandled exception. By contrast, a segfault (at an address other than NULL) would be more interesting from a security perspective.

Re: Do Not Type "File:///" in OS X

#177
post #116

Earlier quoted context omitted.

Great. Now, can you say who ever said that it was voodoo ? I only see someone who said that it was safe to type it in a software, but I can be wrong.

> can you say who ever said that it was voodoo Listing every single app under the sun when it's completely obvious a common and widely used component (doesn't matter what's its name so really no need to know Cocoa and that it's probably NSTextView) is used is acknowledging it as voodoo.

Voodoo is in your mind, perhaps, but not those who found it interesting which apps use NSTextView and which don't.

Right now, Sublime seems to be the only one. Anyone care to try TextMate?

Re: Do Not Type "File:///" in OS X

#179
post #153
post #55

Earlier quoted context omitted.

Add Messages.app to that list, I discovered as I stupidly tried to explain how to repro it to someone..

I dare not try it, but having that text as status on Facebook could crash those viewing my status using Safaris?

No, you have it in the page just fine. It is only when it is in an NSTextField that it becomes an issue.
Post reply on HN