You Are Here:

Community: Blogs

Paul Todd's Forum Nokia Blog

What does this mean for Symbian Signed

Paul.Todd | 14 May, 2007 12:08

I see F-Secure are now apparently flagging two Symbian signed applications as Spyware in their mobile security application.

I follow their blog quite often in my reader and this came up today:
http://www.f-secure.com/weblog/archives/archive-052007.html#00001190

They do not however publish the names of the products concerned.

This does rather interestingly lead to the question of where does Symbian Signed draw the line and just how much trust do we have in it to promote S60 as a safe platform for consumers?

I for one find this very dissapointing as the amount of money we (the company I work for, not a phone manufacturer) are spending on Symbian signed; and the program as a whole to build trust for consumers can so easily be undermined.

I hope the author or Nokia will go into more details about why these applications are flagged....

Hopefully this is just a misunderstanding on the part of F-Secure...

Still it looks like you will need to get AV software for your phone just like Windows

RSSComments

Re: What does this mean for Symbian Signed

mgroeber9110 | 14/05/2007, 12:57

I guess this would bound to happen at some point, but still...

I am not sure if the story in the original blog post completely adds up, and of course the conclusion drawn from this "Still it looks like you will need to get AV software for your phone just like Windows" is probably one that F-Secure is not exactly going to be unhappy about. ;-) So I am wondering if there is a certain amount of "threat hyping" going on here as well.

There are some more details here:

http://www.f-secure.com/sw-desc/spyware_symbos_flexispy_f.shtml

This seems to be a bit of a grey area - an application that has legitmate uses, but at the same time is also capable of being used with malicious intent if you have access to the physical device while it is not locked. But if you have physical access to the device, you are not going to care about Symbian Signed prompts anyway (as you can always enable non-signed installs on any but Softbank KK branded phones).

I think this is different from what most people would think of when they hear "Symbian Signed spyware" - this is not a "trojan" feature in an otherwise "innocent" application, but rather because this application has a certain "dual use" potential, and because it is being being marketed for such uses.

Of course, it is interesting to see what effect that has on Symbian Signed procedures (e.g. the rules governing autostart applications that do not have visible a UI to turn them off).

ciao marcus

Re: What does this mean for Symbian Signed

atirraihan | 20/05/2007, 16:34

Firstly, let me identify myself as a spokesperson for Vervata who are the developers of FlexiSPY.

Let us imagine for a moment, that the next version of FlexiSPY detected the existence of FSecure, and unilaterally decided to identify it as a Virus or Malware, and either disabled FSecure, or advised uninstallation of the FSecure product, would that be justified?

FSecure have set themselves up as judge and jury and refuse to engage in a discussion with Vervata, whose products they are interfering with. Indeed, they are probably on dubious legal grounds here, and this is something that will be interesting to investigate. As I recall, there have been precedents for this kind of action, and the issue of Gator lawsuits comes to mind . However thats an avenue that no one needs to pursue if FSecure would actually respond to contacts from the companies whose products they interfere with.

Lets recall the first release of FlexiSPY, and that FSecure made claims that it could be transmitted and installed without the user knowing what they were doing. Vervata immediately made changes to the dialogues to address these concerns and send copies to FSecure. Did that please FSecure? Of course not! They are more interested in fear mongering about mobile Viruses, as one cant imagine the current threat level of mobile viruses could keep a FSecure engineer busy for more that a few hours per week!

The real question is one of defamation and the freedom to install what you choose on your devices. Let us ask once again, who made them judge and jury regarding commercial, signed applications, that can be traced to the source and makes the nature of its operation blatantly clear. I suspect, as many of us in the industry do, that the issue of Viruses in the mobile space is not significant enough for FSecure to have a business case for their product, but I do understand that they have to earn a living. However, there must be checks and balances, and FSecure need to be accountable for their decisions. Until that happens, developers will have no choice but to ask the user to remove FSecure, or ask for the users permission to kill the FSecure process every time it is detected.

Until FSecure start becoming answerable for their interference with legitimate third party applications, it is FSecure and not Vervata that must be considered a rogue company and producer of Malware.

Re: What does this mean for Symbian Signed

coultonp | 14/05/2007, 20:05

coultonp Paul

This is an interesting one as its advertised as a spying application by the developers I quote

'a mobile phone monitoring application that secretly records all activity on a mobile phone'
'Protect your children, catch cheating partners, the possibilities are endless'

I guess the question is does it break the signing rules?

Re: What does this mean for Symbian Signed

Rippe | 15/05/2007, 10:39

Rippe I think we are talking about http://www.flexispy.com/ ?

This is very interesting matter. The application is intended for spying on what the phone user does and then sending that information to a designated terminal. The information would be for example call logs and SMSs.

Who would use such an application? A jealous spouse? I think that would be obvious use case.

As such the application does not commit a crime. It does not physically hurt the user, it does not do any damage to the data in the device, the thing what it does is it relays information from the phone. Just like a calendar and contacts synchronization application would do.

The crime is committed if the person installing the application to a device does not tell to the user of the device what is being done and how the application behaves. Then the person installing the application would actually break privacy laws. So if the jealous spouse tells that s/he cannot trust the other and to get a peace of mind would need to install this application. Then it is fine. Naturally if I were a jealous spouse, I would install this without telling and there I would break the law.

See the point? A phone can be used to commit crimes, but that does not make the phone illegal. It is the use case.

Re: What does this mean for Symbian Signed

tote_b5 | 15/05/2007, 14:25

tote_b5 Imho it would make sense if the virus databases of respected anti-virus software products were synchronized with the official CRLs (i.e. Certificate Revocation Lists). And the Application Installer can check it out very easily via OCSP (Online Certificate Status Protocol) if an application to be installed is a malware or not. This solution would not require, though, that phone manufacturers be involved in the whole process.

Tote

Re: What does this mean for Symbian Signed

Tompenner | 15/05/2007, 17:09

I disagree with F-Secure's position here.

I have agreed with my children to run such an commercial monitoring applications on their cell phones, for our familiy to be sure where they are and to have limited controll over what they do with their phones.
Also a colleague of mine is using a similar application to continously back-up sent and received text messages and keep a list of made/received phone calls for expense purposes.
From that perspective it is perfectly OK that Symbian gave this application the certificate Symbian Signed.

F-Secure seems to hype this topic for creating a demand for their mobile security.

Re: What does this mean for Symbian Signed

PushL | 15/05/2007, 17:48

I think the misunderstanding with these issues is considering the signing process as some sort of good-behaviour/quality certification. Passing the tests just means among other things that your application has some quality to be usable, but it's certainly impossible (or undecidable) to know whether it contains some trigger which activates some bad behaviour. I can be thought as some sort of "halting problem"

Nothing can stop someone to add some malicious behaviour in a program and get it signed. The difference here is that this "someone" is no longer anonymous. Name & other personal data is given when asking for an ACS.

It would be certainly nice to know either Nokia or Symbian Signed team's opinion, and whether there would be some kind of measure to be taken in such cases.

David.

Re: What does this mean for Symbian Signed

doctordwarf | 15/05/2007, 20:03

doctordwarf It depends on how you view the Symbian Signed. To me the *only* thing that the signature confirms is that the application is indeed developed by the company mentioned in the certificate and it is a real company. It implicitly protects you from many dangers, because a typical malicious hacker wouldn't like to be easily identified. However, I don't think Symbian Signed was even designed to exactly protect anybody from spyware.

Re: What does this mean for Symbian Signed

widianuser | 15/05/2007, 21:38

This is a very interesting topic. Personally I haven't installed virus scanners to any of my own devices as I just can't see the risk of mobile malware for Symbian 9. Hands up, who has seen live Symbian 9 malware spreading wild?

Can we expect to see in the future virus scanners blacklisting native device management application because that can be used to investigate the terminal contents and to change the settings without user interaction? How about Symbian Signed test case GEN-01 that tests the software for "The application does not affect the use of the system features or other applications." If virus scanners begin aggressively blacklisting signed applications, should scanners pass the signing?
You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZdescriptionQSxHiE2cE20IE27mE20PaulE2cE20butE20youE20canE20alsoE20callE20meE20ToddE20andE20IE20wonE27tE20getE20upsetE2eE20PaulE2eToddE20E7cE2014E20MayE2cE202007E2012E3a08E20IE20seeE20FE2dSecureE20areE20nowE20apparentlyE20flaggingE20twoE20SymbianE20signedE20applicationsE20asE20SpywareE20inE20theirE20mobileE20securityE20applicationE2eIE20followE20theirE20blogE20E71uiteE20oftenE20inE20myE20readerE20andE20thisE20cameE20upE20todayE3ahttpE3aE2fE2fwwwE2efE2dsecureE2ecomE2fweblogE2farchivesE2farchiveE2d052007E2ehtmlE2300001190TheyE20doE20notE20howeverE20publishE20theE20namesE20ofE20theE20productsE20concernedE2eThisE20doesE20ratherE20interestinglyE20leadE20toE20theE20E71uestionE20ofE20whereE20doesE20SymbianE20SigneE2eE2eE2eX qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fpaulE2dtoddsE2dforumE2dnokiaE2dblogE2f2007E2f05E2f14E2fwhatE2ddoesE2dthisE2dmeanE2dforE2dsymbianE2dsignedX qdcZpublisherQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fidE2fc764fd1cE2d8b06E2d499aE2d9a6aE2d17c3903d5a65E2fforumE5fnokiaE5fcrawlerE5fagentX qdcZtitleQSxPaulE20ToddE27sE20ForumE20NokiaE20BlogE20E7cE20WhatE20doesE20thisE20meanE20forE20SymbianE20SignedX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZBlogE45ntryQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qrssZdescriptionQSxHiE2cE20IE27mE20PaulE2cE20butE20youE20canE20alsoE20callE20meE20ToddE20andE20IE20wonE27tE20getE20upsetE2eE20PaulE2eToddE20E7cE2014E20MayE2cE202007E2012E3a08E20IE20seeE20FE2dSecureE20areE20nowE20apparentlyE20flaggingE20twoE20SymbianE20signedE20applicationsE20asE20SpywareE20inE20theirE20mobileE20securityE20applicationE2eIE20followE20theirE20blogE20E71uiteE20oftenE20inE20myE20readerE20andE20thisE20cameE20upE20todayE3ahttpE3aE2fE2fwwwE2efE2dsecureE2ecomE2fweblogE2farchivesE2farchiveE2d052007E2ehtmlE2300001190TheyE20doE20notE20howeverE20publishE20theE20namesE20ofE20theE20productsE20concernedE2eThisE20doesE20ratherE20interestinglyE20leadE20toE20theE20E71uestionE20ofE20whereE20doesE20SymbianE20SigneE2eE2eE2eX qfnZdistributionQUxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fX qfnZtopicQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fFNE2d1E2fBlogTopicE2fgeneralXRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZseriesE5f60QRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZtestingQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZBlogE45ntryQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZupdatedQDx2007E2d05E2d20X qfnZuserE5ftagQSxs60X qfnZuserE5ftagQSxtestingX qmarsZdescriptionQSxHiE2cE20IE27mE20PaulE2cE20butE20youE20canE20alsoE20callE20meE20ToddE20andE20IE20wonE27tE20getE20upsetE2eE20PaulE2eToddE20E7cE2014E20MayE2cE202007E2012E3a08E20IE20seeE20FE2dSecureE20areE20nowE20apparentlyE20flaggingE20twoE20SymbianE20signedE20applicationsE20asE20SpywareE20inE20theirE20mobileE20securityE20applicationE2eIE20followE20theirE20blogE20E71uiteE20oftenE20inE20myE20readerE20andE20thisE20cameE20upE20todayE3ahttpE3aE2fE2fwwwE2efE2dsecureE2ecomE2fweblogE2farchivesE2farchiveE2d052007E2ehtmlE2300001190TheyE20doE20notE20howeverE20publishE20theE20namesE20ofE20theE20productsE20concernedE2eThisE20doesE20ratherE20interestinglyE20leadE20toE20theE20E71uestionE20ofE20whereE20doesE20SymbianE20SigneE2eE2eE2eX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZBlogE45ntryQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ