Data security
Marco Martin
notmart at gmail.com
Thu Jan 5 19:23:12 UTC 2012
Hi all,
there is a thing that is still missing pretty much completely, and was part of
the feature plan since the beginning...
it's an (admittely) pretty vague security model for the data stored on the
device.
now, this can mean different things:
* security of the device itself against stealing: how much can be done about
is kinda limited, apart some usual, as low level as possible things such as
full disk encryption (and possibly some way to shut it down remotely). This is
something that would add a real value compared to other mobile platforms
around
* security model of the data even against the applications: should be the
nepomuk store doing some sort of authentication on who can access it and what
data? this could be desiderable as well, not sure about the technical
feasability tough, in part because all our stuff communicates with the easily
eavesdroppable dbus (nepomuk, contour, activity manager), in part because
whatever you can really sandbox an installed c++ app is a bit questionable.
probably at least some form of authentication for qml only stuff to the
metadata model and the dataengines is desiderable *and* feasible tough.
maybe with a derivation of the remote plasmoid authorization?
Cheers,
Marco Martin
More information about the Active
mailing list