• 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: Allocating too much memory kills my App rather than returning NULL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Allocating too much memory kills my App rather than returning NULL


  • Subject: Re: Allocating too much memory kills my App rather than returning NULL
  • From: Jeff Kelley <email@hidden>
  • Date: Wed, 09 Nov 2011 11:06:36 -0500

On Wed, Nov 9, 2011 at 3:08 AM, Don Quixote de la Mancha <
email@hidden> wrote:

>
> While the iOS and Mac OS X do have a better security track record than
> Windows does, I'm quite certain that's because "The Scene" has been
> focussing on Windows due to its greater numbers.  With Apple's
> increasing financial success, malware such as Mac Defender is starting
> to crop up.
>

Mac Defender was a scam app that the user had to download and run. That’s
barely malware, and can by definition happen on any platform that allows
users to run downloaded code. Code Red, on the other hand, could infect a
server running IIS without user interaction. They really could not be more
different from a security perspective.


> Apple's security update to fix the Mac Defender exploit was a gigabyte
> download - compressed!  That suggests that whatever holes Apple
> plugged were all over creation.
>

Or that the files involved were big. Apple’s patches aren’t binary diffs,
so if you patch a 200MB file with a one-line change, that whole file is
still included in the update package.
_______________________________________________

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: Allocating too much memory kills my App rather than returning NULL
      • From: Scott Ribe <email@hidden>
References: 
 >Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Jens Alfke <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Greg Parker <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Wade Tregaskis <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Joar Wingfors <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Wade Tregaskis <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Kyle Sluder <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Greg Parker <email@hidden>)
 >Re: Allocating too much memory kills my App rather than returning NULL (From: Don Quixote de la Mancha <email@hidden>)

  • Prev by Date: Re: Custom About Box with background shape
  • Next by Date: Re: ObjC's flat and all-exported namespace, help!
  • Previous by thread: Re: Allocating too much memory kills my App rather than returning NULL
  • Next by thread: Re: Allocating too much memory kills my App rather than returning NULL
  • Index(es):
    • Date
    • Thread