Subject:
|
Re: Making the DAT links work in safari.
|
Newsgroups:
|
lugnet.cad.dev.mac
|
Date:
|
Fri, 23 May 2008 14:24:34 GMT
|
Viewed:
|
11442 times
|
| |
|
|
In lugnet.cad.dev.mac, Christopher Masi wrote:
> In the Mozilla progeny, the ability to specify a helper application
> still exists
>
> It would be cool to if we could get Safari to behave similarly, but I am
> unwilling to give Safari the blanket permission to open all files _it_
> considers safe, especially since I don't control what Safari considers
> to be a safe or unsafe file types. I'm willing to accept the security
> risk posed by the automated passing of a dat file to LDGLite, because,
> well, frankly, even if LDGLite has gaping security holes, what are the
> odds that someone is going to write an exploit for it? (It doesn't have
> gaping security holes, does it Don :)
Hi Chris, it's like swiss cheese, but let's keep that a secret.
> So, I guess I'm suggesting a switch to a Mozilla based browser that will
> allow you to specify what the browser should do when presented with
> new/unknown mime types. Safari just isn't equipped to hand it
> gracefully, which is too bad really :(
>
> By the way, I did bring this up a few years ago when you and I used to
> talk about LDGLite more, Don :)
Yeah I remember, but now I actually have a junky used Mac of my own to
play with, so I want to learn as much as I can before it dies. I was
sorta assuming Mozilla still worked and was trying to see what I could
squeeze out of Sarari, since it comes with OS-X and seems to work pretty
well otherwise. I still have to experiment with LSRiskCategroyNeutral
and maybe a wrapper plugin to see if those options provide better
security control than the blanket "Give me everything Safe" setting.
I'm not sure how Safari handles plugins, but if it could automatically
launch an ldraw viewer from a plugin without the blanket unsafe setting
that'd be a reasonably secure option, right?
Anyhow, Safari plugins are on the backburner because right now I'm
trying to sort how to work around the bugs in LaunchServices. It's a
cool idea; letting the individual apps each stake a claim to the file
types in their own individual info.plist files. That way the apps can
be self contained and portable. But judging from my (recent)
experiences and the numerous bug reports on the internet, it doesn't
seem to work so well in the real world. So far, I've been unable to
shake L3Lab from it's unholy grip on my .dat files. :^)
Enjoy,
Don
|
|
Message has 1 Reply:
 | | Re: Making the DAT links work in safari.
|
| (...) [...] (...) Mmmm... I like swiss cheese too (...) Oops sorry. I shouldn't have assumed that you forgot those conversations. It would be cool if you could get Safari to do it. (...) It would allow the user to select which things to be (...) (17 years ago, 23-May-08, to lugnet.cad.dev.mac)
|
Message is in Reply To:
| | Re: Making the DAT links work in safari.
|
| (...) OK, long time Mac users here. In the days of long ago, most/all browsers could be configured so that when the browser didn't know what to do with a file, a helper application, specified by the user, could jump in to open the file for you. (I (...) (17 years ago, 23-May-08, to lugnet.cad.dev.mac)
|
15 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
