just crashing the app.
> Cheers.
>
>> Subject: Re: NSSecureCoding with containers (or, is NSArray lying?)
>> From: graham@bigpond.com
>> Date: Fri, 17 Jul 2015 09:52:33 +1000
>> CC: r...@rols.org; cocoa-dev@lists.apple.com
>> To: andre.frate...@hotmail.com
threat is just crashing the app.
Cheers.
> Subject: Re: NSSecureCoding with containers (or, is NSArray lying?)
> From: graham@bigpond.com
> Date: Fri, 17 Jul 2015 09:52:33 +1000
> CC: r...@rols.org; cocoa-dev@lists.apple.com
> To: andre.frate...@hotmail.com
>
>
&g
> On 16 Jul 2015, at 12:17 pm, André Francisco
> 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
nice to know, though, as this could possibly
introduce security issues in an app.
Thanks a lot!
Subject: Re: NSSecureCoding with containers (or, is NSArray lying?)
From: r...@rols.org
Date: Thu, 16 Jul 2015 10:44:55 +0800
CC: cocoa-dev@lists.apple.com
To: andre.frate...@hotmail.com
The list of thing
ys of my own objects.
>
> Anyway, based on all my research, SO comments, and especially this
> conversation, I have been becoming more and more convinced that there doesn't
> exists a real solution. NSSecureCoding doesn't seem so secure anymore :\
>
>
> > Subject:
nyway, based on all my research, SO comments, and especially this
conversation, I have been becoming more and more convinced that there doesn't
exists a real solution. NSSecureCoding doesn't seem so secure anymore :\
> Subject: Re: NSSecureCoding with containers (or, is NSArray lying?)
> On 16 Jul 2015, at 08:30, André Francisco wrote:
>
> Hi all,
> I posted a question at SO
> (http://stackoverflow.com/questions/31307331/how-to-use-nssecurecoding-with-id-objects)
> and despite the bounty it still didn't get any answers. I am not confident
> that it will either.
> The proble
