Do Not Type "File:///" in OS X • Hacker News Board

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

#191

Post by yuhong » Sun, Feb 03, 2013, 1:36 AM UTC

lloeki wrote: post #138

niggler wrote: post #132

Earlier quoted context omitted.

Backwards compatibility refers to newer software/hardware not supporting older software/hardware. For example, Apple axed the rosetta powerpc support (which allowed you to run older software after apple switched to intel CPUs) in Leopard. I still keep a PowerBook G4 just for MacDraw.

Rosetta is optional but supported on Snow Leopard, and gets downloaded automatically on demand. Seven years of transition (assuming SL stopped to be supported when ML was released) to Intel was more than enough for active software to be ported. You just can't carry legacy code indefinitely, you have to stay focused or you'll be all over the place and suffer death by a thousand cuts.

>(assuming SL stopped to be supported when ML was released)

Which they backed off from. You can probably thank Flashback for that.

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

#192

Post by TvFreak » Sun, Feb 03, 2013, 2:51 AM UTC

File:///

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

#193

Post by niggler » Sun, Feb 03, 2013, 3:29 AM UTC

asveikau wrote: post #184

niggler wrote: post #53

Earlier quoted context omitted.

I try to avoid upgrading OSX. When a new version comes out, I wait for a hardware refresh and just get a new Mac (Apple has a nasty habit of disregarding backwards compatibility, and it's really nice to be able to do stuff like run older powerpc programs) EDIT: the [deleted] comment was 'I miss snow leopard'

> When a new version comes out, I wait for a hardware refresh and just get a new Mac Apple must love you.

When you have a business, its far easier to just purchase a new machine and expense it than it is to upgrade existing machines. Time is far more value than money, and I'd much rather spend 3K for a new machine than waste a day or a week struggling with an upgrade issue and dealing with AppleCare.

PS: it's eligible for section 179 accelerated depreciation and sales-tax free in NY thanks to ST 121.3

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

#194

Post by frostnovazzz » Sun, Feb 03, 2013, 5:02 AM UTC

Works fine in sublime text 2

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

#195

Post by asveikau » Sun, Feb 03, 2013, 6:31 AM UTC

niggler wrote: post #193

asveikau wrote: post #184

Earlier quoted context omitted.

> When a new version comes out, I wait for a hardware refresh and just get a new Mac Apple must love you.

When you have a business, its far easier to just purchase a new machine and expense it than it is to upgrade existing machines. Time is far more value than money, and I'd much rather spend 3K for a new machine than waste a day or a week struggling with an upgrade issue and dealing with AppleCare. PS: it's eligible for section 179 accelerated depreciation and sales-tax free in NY thanks to ST 121.3

Please note my reply was meant to be taken as a joke. I expect most people don't need to refresh their Apple gear on a yearly basis, but that is a bit of the stereotype of an enthusiastic Apple fan, and your post can be taken humorously to fit that image. Of course with Apple the answer is always more hardware. :-)

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

#196

Post by Flow » Sun, Feb 03, 2013, 9:12 AM UTC

0x0 wrote: post #156

Flow wrote: post #154

Earlier quoted context omitted.

Doesn't crash my Terminal.app. I use a swedish keyboard. Perhaps you could create a new clean account on your computer and try it there? You can always delete the account afterwards.

Interesting. Must be some kind of pref setting or something that's surfacing the bug. Ugh, sounds hard to track down.

Yup, and that's why I suggests you create a new fresh user and try it there. If the bug doesn't show there it's something in your personal settings somewhere, if not it's in the system settings.

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

#197

Post by seppler » Sun, Feb 03, 2013, 10:23 AM UTC

chromejs10 wrote: post #171

mathrawka wrote: post #104

Earlier quoted context omitted.

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?

This will remove any messages from your iMessage database that contain %File:% (% is a wildcard):

sqlite3 ~/Library/Messages/chat.db "delete from message where text like "%File:%"

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

#198

Post by josteink » Sun, Feb 03, 2013, 3:34 PM UTC

Also, do not send file:/// to anyone using iMessage on their computer.

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

#199

Post by thefreeman » Sun, Feb 03, 2013, 5:17 PM UTC

pcwalton wrote: post #175

thefreeman wrote: post #164

Earlier quoted context omitted.

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.

thank you sir!

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

#200

Post by alttab » Sun, Feb 03, 2013, 6:53 PM UTC

Firehed wrote: post #115

jzwinck wrote: post #94

Earlier quoted context omitted.

Would you have the standard text field run in a separate process sandbox? Or not have standard widgets shared between apps? Or just try real hard to write code without bugs?

Uh, no - this is more of a "don't execute code in a textbox" thing.

A great way around this would be for the system to ignore exceptions unless it was caught... wait nevermind