Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: NSSecureCoding with containers (or, is NSArray lying?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSSecureCoding with containers (or, is NSArray lying?)

Subject: Re: NSSecureCoding with containers (or, is NSArray lying?)
From: Graham Cox <email@hidden>
Date: Fri, 17 Jul 2015 09:52:33 +1000

> On 16 Jul 2015, at 12:17 pm, André Francisco <email@hidden> wrote:
>
> This can easily crash an app if I get a type that I'm not expecting, even if it implements NSSecureCoding.

Actually, probably not. It will likely start throwing exceptions all over the place, which *may* cause termination, but it won’t crash in a way that could lead to an exploit.

—Graham

_______________________________________________

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: NSSecureCoding with containers (or, is NSArray lying?)
  - From: André Francisco <email@hidden>

References:
	>NSSecureCoding with containers (or, is NSArray lying?) (From: André Francisco <email@hidden>)
	>Re: NSSecureCoding with containers (or, is NSArray lying?) (From: Roland King <email@hidden>)
	>RE: NSSecureCoding with containers (or, is NSArray lying?) (From: André Francisco <email@hidden>)

Prev by Date: Re: Integrating touch Id with sign up-in process in client-server based app
Next by Date: Re: Safe time to add accessory view to NSSavePanel in sandboxed app?
Previous by thread: RE: NSSecureCoding with containers (or, is NSArray lying?)
Next by thread: RE: NSSecureCoding with containers (or, is NSArray lying?)
Index(es):
- Date
- Thread