> -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of ext Samir Faci (Dev) > Sent: 29 March, 2010 06:19 > To: [email protected] > Subject: [MeeGo-dev] Meego Market? > > I'm just curious how the Meego will be structured? Since the entire > meego platform is very much about openness and freedom and giving the > developer the choice to write code the way he wants. > > Theoretically If I don't particularly care about gps/gestures. I > could write an app for the meego platform from BF (brain fu**) to > C++/QT, Java and everything in between. > > I'm just wondering how the market will be sanitized. Is anything > going to put in place to prevent rogue processes from bring down your > phone?
In the architecture picture [1] there is a yellow bar on the side called SECURITY. It will stop the application from doing things that it is not supposed to do, like bring the device down. > Most importantly, how is security going to be death with? I would > think someone could easily develop and write an application that is > malicious and call back home with personal information of the user > that he shouldn't have. Probably yes, but the application needs to be delivered and installed somehow. Let's assume that there are a lot of people who are stupid enough to install applications without any thought on what the application does. Where would someone share that malicious application? Or then you are talking about proper viruses, which don't need repositories. But the people writing those aren't going to care about the rules anyway. And handling that is up to system security. The core repositories are not taking in content from random people. The community repositories will likewise have a process for checking incoming code. And commercial software markets all have pretty tight QA in place. Anyway, that leaves the person who wants to crash a device with the option of setting up a new repository, getting people to somehow add that and install the malware from there. How will people (especially the target audience, who are fairly clueless because they aren't afraid of random code) do that, especially after word is out that it contains malware? And of course on top of that problem you have the yellow bar in the architecture saying security, which hopefully will be cleared a bit more after there is code out. So yes, both technical and social measures are being put into place to prevent malware. Tero // I am not an architect. I deal with community web services, so my depth of knowledge in this area is limited. [1] http://meego.com/developers/meego-architecture > -- > Samir Faci > PS. I hope I don't start another massive thread like my previous email > (N900 Questions) > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
