Joke of the week
Here's a "nice" story about Symbian Signed from a fellow developer:
And congrats for FCA00000 for his great platform security discoveries on TRK! TRK is one application that would never get signed by Symbian Signed, just try starting debug and (accidentally) disconnect the USB cable ;)
Our application has a disclaimer statement on first startup - required by the Symbian Signed, because we are sending SMS messages. First few rounds of Symbian Signed passed well, but now we FAILED:
The disclaimer statement is not shown again if the user kills application using taskmanager while the disclaimer statement is on screen.
We have implemented the disclaimer as a note which is shown when our configuration settings are not found. But, as we start application, the engine writes the missing settings file - so next time it won't get shown.
Now we have to create another file just to get this "problem" fixed! Total B.S! [Note to self - remember to add into backup]
And congrats for FCA00000 for his great platform security discoveries on TRK! TRK is one application that would never get signed by Symbian Signed, just try starting debug and (accidentally) disconnect the USB cable ;)
posted by manko at
Thursday, March 13, 2008
4 Comments:
Sounds pretty odd to me as there's no criteria in Symbian Signed that would require a note to be shown the user if the application sends an SMS message. It would be "nice" to know the whole story behind the case.
I believe it's called "Privacy Statement" which has to be shown on install and first startup.
There's no such thing as "privacy statement" in Symbian Signed criteria anymore. That's why it would be nice to know the whole story. Or this case is pretty old...
Could Symbian 9.2 be hacked now?
I failed on E51.
Post a Comment
Links to this post:
Create a Link
<< Home