• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Problem with stopModalWithCode on a different thread
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with stopModalWithCode on a different thread


  • Subject: Re: Problem with stopModalWithCode on a different thread
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 23 Jun 2010 00:19:39 -0700

On Jun 22, 2010, at 7:49 PM, Bill Appleton wrote:

> i am pointing out that there is a giant, giant, giant difference between plugins that impose themselves on the user and those that are invoked because the user wants them.

Plugins don’t impose themselves, nor are they invoked by a user; they’re always invoked by content on a web page. The user might go to that web page specifically to use the plugin, or it might be a side effect, but the mechanism is the same regardless.

> all of the security stuff you are talking about is appropriate for the former. all of this security stuff just makes users of the latter pissed off.

No, the ‘security stuff’ is appropriate regardless. If a bunch of people install your plugin, and if someone were to find a security hole in it that lets them do something nasty to your computer, then websites would inevitably pop up that invoked your plugin and exploited the bug.

Note that web plugins are more susceptible to attack than regular apps because, once installed, they can be invoked and run _automatically_ by web content, with absolutely no warning and no permission needed by the user. The user might not even know that it’s running. This makes web plugins probably the most potentially-dangerous type of software you can install.

> this is absolutely key. we have 10 K companies that desperately need a simple way to install and use our player. this is mission critical for them.

Simplicity and convenience don’t usually go along with security, unfortunately. For example, ActiveX was a very simple and convenient way to extend the web experience (in MSIE on Windows at least), and it became a big part of why Windows had so many security problems.

—Jens_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Problem with stopModalWithCode on a different thread
      • From: Bill Appleton <email@hidden>
References: 
 >Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Jens Alfke <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Charles Srstka <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Charles Srstka <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Charles Srstka <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Jens Alfke <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Charles Srstka <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Charles Srstka <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Jens Alfke <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Jens Alfke <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)
 >Re: Problem with stopModalWithCode on a different thread (From: Bill Appleton <email@hidden>)

  • Prev by Date: Re: Isolate NSTextView from NSColorWell
  • Next by Date: Re: Incomplete rendering returned from glReadPixels
  • Previous by thread: Re: Problem with stopModalWithCode on a different thread
  • Next by thread: Re: Problem with stopModalWithCode on a different thread
  • Index(es):
    • Date
    • Thread