![]() |
Sailfish: Security / Privacy
Sorry, this may have been discussed in seperate threads before, but i think, it needs an own thread:
as rainisto said, there is no NSA backdoor in Sailfish, thanks for that! ...but what about the typical "fart app" usecase? can some stupid android app read your complete device and send the data to some suspicious server or is such thing completely impossible? ... and what about native apps? is there some control or do you just have to be faithfull and trust every native app automatically? i never had a problem with that on Fremantle / Harmattan, but i can imagine, Sailfish will become much more popular, hence much more attractive to possible "attackers"... |
Re: Sailfish: Security / Privacy
Android apps will not have access to sailfish native data (nemo-user guid vs privileged IIRC), no worries about background calls/sms too, no way to call/send text without user physically hitting the button and all attempts to call should invoke native dialer/texter (all this is from the user experience/cancelled preorder and tracking numbers threads). Not sure if android apps have their own storage for such data that can be 'flashlighted' away
|
if you never enable developer mode you can no worry about that.
|
Re: Sailfish: Security / Privacy
Quote:
|
Re: Sailfish: Security / Privacy
All devices have back doors. It's just that you don't know about the holes yet.
|
Re: Sailfish: Security / Privacy
Quote:
which button are you talking about, exaclty...
any way, hacking into 50'000+ devices at an early alpha stage (except for the UI which seems to be fairly smooth... do i sense the usual nemo / Mer C like crap here?!? :eek: community = NOT working :mad:) does not make much sense for any hacker, just not worth the effort considering the development needed to get it done couple thoughts about posts on this thread...
EDIT: typo |
Re: Sailfish: Security / Privacy
Quote:
So yes, in future Android malware might be able to steal your local contacts but the same malware most likely can steal the same data on any Android device (but its still not able to make phonecalls nor send sms'es without user interaction). As the things that can cause you loose real money is the thing that we try to protect better. And even when contact data is valueble, protecting that too tightly eats usability from Whatsup like applications. So installing random apk packages blindly from Internet is your own decision as they will have readonly access to unprotected nemo data (but we do protect that android apps cannot send hidden sms'es nor make phonecalls.). Also at some point in the future you might also be able to choose if some contact is local or privileged. N900 and N9 sold seven figure amounts and didn't have problem with malware, so I doubt that malware writers will bother looking into Sailfish OS untill our sales figures have reached the same (or have reached 8 or 9 figures). And if some day someone releases 1st Sailfish specific malware application, then we will react to it and tighten the holes if need be. Untill that this all is just specilative ranting. Linux generally is quite open system with Unix directory permissions (and you don't see that much malware in there), and we are trying to follow those footsteps (+ protecting hidden phonecall / sms sending). |
Maybe Whatsapp made a official client for sailfish
|
Re: Sailfish: Security / Privacy
Quote:
AFAIK the device being Mer-based is one of the real reasons I was intrested in it in the first place :) The UI is nice but the openness/hackability is the prime attraction fature for me. |
Re: Sailfish: Security / Privacy
Quote:
Quote:
|
All times are GMT. The time now is 03:35. |
vBulletin® Version 3.8.8