Re: Nokia more open than he thinks
That's not entirely true Dominic. You can allow "self signed" apps to be installed by changing a menu setting which grants the application. This allows you to install applications with very basic capabilities (LocalServices,• UserEnvironment,• NetworkServices, ReadUserData,WriteUserData).
On install, the user is told about the basic capabilities that the app requires and can abort or continue to install. (Bruce Shneier has some good material on his blog regarding the problems with asking the user to make security decisions).
A posting on forum nokia indicates that around 60% of the APIs on S60 are available to self signed applications, which does actually give then developer a fair set of APIs to play with. You can draw to the screen, pop up dialogs, persist data to the app's home directory and quite a bit more.
Sensitive services (meaning - access to user's personal data, location or services that can spend money) are only available through the Symbian signed process.
The option that you are seeing on the E61 can be configured by the handset manufacturer/operator. In fact, if they wish, they can hardcode devices to only allow Symbian signed apps if they feel that the self signed criterion is too liberal.
I think it's sensible that Apple at least wait until they get the security model raionalised and tested by their close partners before opening up the phone. It's very hard to close off an API after it has been open and used and relied on by 3rd parties.
When building a open device, you want some level of sandboxing not just for security marshalling but also to allow the core code to evolve and be re-factored without breaking 3rd party apps in each update. If I was Steve - I wouldn't rush anything either.