Seemingly buckling under massive pressure from developers and users, Orange is now backing down on the code signing requirements for its Orange SPV - or at least partly.
Opting early on to implement the strongest level of application security available in Microsoft's Smartphone 2002 platform for its Orange SPV, the mobile network operator has been under massive fire from both developers and owners since its introduction. Now, after seeing a code signing workaround spreading like wildfire within both groups, Orange is seemingly buckling under the pressure and removing code signing requirements - but only partly so, as only developers will be at a benefit for now.
Developers have long expressed dismay with Orange's requirement for the former to undergo a costly process to have their applications approved. Not only was this previously necessary to be able to sell applications to Orange SPV users, but also for developers to even be able to run beta code on an actual SPV rather than in a software emulator. The most recent development in this matter shows that Orange has been lending an ear to an increasingly vociferous choir of developers, and will now allow these to run beta code on Orange SPVs without it being signed first.
Developers can now purchase an SPV development kit directly from Orange for approximately 450 EUR that comes with the necessary modifications to run beta code, while owners of existing development kits can download an update over-the-air to enable the same functionality in their devices. However, Orange still requires developers to undergo the code signing process to be able to sell finished applications to Orange SPV owners, and is implementing strict routines to ensure only developers download and apply the update.
The process of unlocking the SPV for owners of existing developer kits involves the temporary removal of the certificates. After application development has taken place, developers are required to re-lock the device and re-instate the certificates for the testing procedure to be completed. Once the device is re-locked, unsigned applications will no longer run on the device, a procedure which - despite providing at least an incremental improvement - could potentially harvest more criticism from developers, as those working on multiple projects simultaneously or consecutively would have to carry it out repeatedly.
 |
|
|
|
|
|
Archive