Re: [swift-evolution] executing a string

2016-07-14 Thread Tino Heth via swift-evolution
Turning strings into selectors is a powerful feature as well ;-) — but afaik, Swift doesn't use another sort of special dispatch besides what is known from other languages. ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.o

Re: [swift-evolution] executing a string

2016-07-14 Thread Saagar Jha via swift-evolution
Here’s how selectors in Swift work, based on this proposal. Swift’s selectors are a lot safer than Objective-C’s. > > > > > One of

Re: [swift-evolution] executing a string

2016-07-14 Thread Karl via swift-evolution
> On 14 Jul 2016, at 17:48, Ford Prefect via swift-evolution > wrote: > > One of the major security flaws of Obj C is > the ability to convert a string into a selector, which > permits using private methods by constructing selectors > at runtime long after the app store review has been complete

Re: [swift-evolution] executing a string

2016-07-14 Thread Félix Cloutier via swift-evolution
I've never heard of an app being exploited through selector abuse. Do you have any example of that? Félix > Le 14 juil. 2016 à 08:48:53, Ford Prefect via swift-evolution > a écrit : > > One of the major security flaws of Obj C is > the ability to convert a string into a selector, which > perm

Re: [swift-evolution] executing a string

2016-07-14 Thread Josh Parmenter via swift-evolution
I could see a method being implemented that does something bad, but isn’t called directly anywhere in code. A code path analysis of a program may miss the problematic method (though unlikely?). But if the method signature is passed in dynamically as the result of a web call or something, it coul