We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-01-03 21:14:50 +0200

API Security Model

(see here for more info on what i mean with API)

apps should be able to call API, but there should be some kind of simple, non-limiting and easy way to secure these API's

  1. first, i was thinking that a general access listing could be provided by Jolla, since all apps and OS have these API's, the Jolla people can decide on a sane default access for each API, (eg: no mail/sms/social_media/etc... )
  2. secondly, these should be editable on each device seperately
  3. app installs or updates should extend this list (with the default access level (none, ask, certain apps, all)
  4. if an app starts for the first time (or update, or an API has become installed), (if the level is ask) the system should notify the user that this app, he's running for the first time, is requesting this or that API from other apps or system that if they want to or not. at this point, the user can select ask later, or allow (for now) or whatever action for each API independantly
  5. Since users can modify default, they could for example select that facebook API's (all, or selection) are always denied
  6. the good point now, is that APP that want this kind of API, should still run.
  7. This allows for instance to run games and not want these games to post scores on facebook
  8. This also allows for apps to send emails or sms automatically, without confirmation, because the users would have validated this, or have access to contacts or whatever...

The sky is the limit here as well...

API Security Model

(see here for more info on what i mean with API)

apps should be able to call API, but there should be some kind of simple, non-limiting and easy way to secure these API's

  1. first, i was thinking that a general access listing could be provided by Jolla, since all apps and OS have these API's, the Jolla people can decide on a sane default access for each API, (eg: no mail/sms/social_media/etc... )
  2. secondly, these should be editable on each device seperately
  3. app installs or updates should extend this list (with the default access level (none, ask, certain apps, all)
  4. if an app starts for the first time (or update, or an API has become installed), (if the level is ask) the system should notify the user that this app, he's running for the first time, is requesting this or that API from other apps or system that if they want to or not. at this point, the user can select ask later, or allow (for now) or whatever action for each API independantly
  5. Since users can modify default, they could for example select that facebook API's (all, or selection) are always denied
  6. the good point now, is that APP that want this kind of API, should still run.
  7. This allows for instance to run games and not want these games to post scores on facebook
  8. This also allows for apps to send emails or sms automatically, without confirmation, because the users would have validated this, or have access to contacts or whatever...

The sky is the limit here as well...

API Security Model

(see here for more info on what i mean with API)

apps should be able to call API, but there should be some kind of simple, non-limiting and easy way to secure these API's

  1. first, i was thinking that a general access listing could be provided by Jolla, since all apps and OS have these API's, the Jolla people can decide on a sane default access for each API, (eg: no mail/sms/social_media/etc... )
  2. secondly, these should be editable on each device seperately
  3. app installs or updates should extend this list (with the default access level (none, ask, certain apps, all)
  4. if an app starts for the first time (or update, or an API has become installed), (if the level is ask) the system should notify the user that this app, he's running for the first time, is requesting this or that API from other apps or system that if they want to or not. at this point, the user can select ask later, or allow (for now) or whatever action for each API independantly
  5. Since users can modify default, they could for example select that facebook API's (all, or selection) are always denied
  6. the good point now, is that APP that want this kind of API, should still run.
  7. This allows for instance to run games and not want these games to post scores on facebook
  8. This also allows for apps to send emails or sms automatically, without confirmation, because the users would have validated this, or have access to contacts or whatever...

The sky is the limit here as well...