touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #21423
[Bug 1374577] Re: 'unconfined' should be precached and not listed under 'Location access' (or 'Other app access')
** Package changed: trust-store (Ubuntu) => location-service (Ubuntu)
** Description changed:
If I go to Location access under Security & Privacy, I have an entry in
the list that is blank. I'm not sure what this is but I'm assuming it is
for 'unconfined' ('unconfined' should be precached to default to 'allow'
anyway).
We should not allow the user to adjust entries for 'unconfined'
processes in System Settings since this might break things in unexpected
ways. Marking as Critical and for rtm14 because this is user facing,
confusing to have a blank entry, can lead to unexpected behavior and
because it should be trivial to filter this out.
- Steps to reproduce:
+ Steps to reproduce (this resets the location trust-store db):
1. $ stop ubuntu-location-service-trust-stored
2. mv ~/.local/share/UbuntuLocationService/trust.db ~/.local/share/UbuntuLocationService/trust.db.bak
3. $ start ubuntu-location-service-trust-stored
4. launch webbrowser-app (it is unconfined)
5. navigate to maps.google.com. it will prompt to access location (browser prompt). Say yes
At this point I am presented with a trust session prompt:
"unconfined
An unconfined application wants to access your current location.
Deny
Allow"
6. tap 'Allow'
This adds the following to the trust store:
3|unconfined|0|1411758762544069109|1
location service shouldn't be prompting for this for the reasons
outlined above. Adding location-service task.
This will likely affect camera and mic in 'Other app access'.
** Description changed:
If I go to Location access under Security & Privacy, I have an entry in
- the list that is blank. I'm not sure what this is but I'm assuming it is
- for 'unconfined' ('unconfined' should be precached to default to 'allow'
- anyway).
+ the list that is blank which corresponds to 'unconfined' ('unconfined'
+ should be precached to default to 'allow' anyway).
We should not allow the user to adjust entries for 'unconfined'
processes in System Settings since this might break things in unexpected
ways. Marking as Critical and for rtm14 because this is user facing,
confusing to have a blank entry, can lead to unexpected behavior and
because it should be trivial to filter this out.
Steps to reproduce (this resets the location trust-store db):
1. $ stop ubuntu-location-service-trust-stored
2. mv ~/.local/share/UbuntuLocationService/trust.db ~/.local/share/UbuntuLocationService/trust.db.bak
3. $ start ubuntu-location-service-trust-stored
4. launch webbrowser-app (it is unconfined)
5. navigate to maps.google.com. it will prompt to access location (browser prompt). Say yes
At this point I am presented with a trust session prompt:
"unconfined
An unconfined application wants to access your current location.
Deny
Allow"
6. tap 'Allow'
This adds the following to the trust store:
3|unconfined|0|1411758762544069109|1
location service shouldn't be prompting for this for the reasons
outlined above. Adding location-service task.
This will likely affect camera and mic in 'Other app access'.
** Description changed:
If I go to Location access under Security & Privacy, I have an entry in
the list that is blank which corresponds to 'unconfined' ('unconfined'
should be precached to default to 'allow' anyway).
- We should not allow the user to adjust entries for 'unconfined'
- processes in System Settings since this might break things in unexpected
- ways. Marking as Critical and for rtm14 because this is user facing,
- confusing to have a blank entry, can lead to unexpected behavior and
- because it should be trivial to filter this out.
+ We should not prompt the user for unconfined or allow the user to adjust
+ entries for 'unconfined' processes in System Settings since this might
+ break things in unexpected ways. Marking as Critical and for rtm14
+ because this is user facing, confusing to have a blank entry, can lead
+ to unexpected behavior and because it should be trivial to filter this
+ out.
Steps to reproduce (this resets the location trust-store db):
1. $ stop ubuntu-location-service-trust-stored
2. mv ~/.local/share/UbuntuLocationService/trust.db ~/.local/share/UbuntuLocationService/trust.db.bak
3. $ start ubuntu-location-service-trust-stored
4. launch webbrowser-app (it is unconfined)
5. navigate to maps.google.com. it will prompt to access location (browser prompt). Say yes
At this point I am presented with a trust session prompt:
"unconfined
An unconfined application wants to access your current location.
Deny
Allow"
6. tap 'Allow'
This adds the following to the trust store:
3|unconfined|0|1411758762544069109|1
location service shouldn't be prompting for this for the reasons
outlined above. Adding location-service task.
This will likely affect camera and mic in 'Other app access'.
** Description changed:
If I go to Location access under Security & Privacy, I have an entry in
the list that is blank which corresponds to 'unconfined' ('unconfined'
should be precached to default to 'allow' anyway).
We should not prompt the user for unconfined or allow the user to adjust
entries for 'unconfined' processes in System Settings since this might
break things in unexpected ways. Marking as Critical and for rtm14
because this is user facing, confusing to have a blank entry, can lead
- to unexpected behavior and because it should be trivial to filter this
- out.
+ to unexpected behavior, it should be trivial to filter this out in
+ system settings and because it should be easy to precache this.
Steps to reproduce (this resets the location trust-store db):
1. $ stop ubuntu-location-service-trust-stored
2. mv ~/.local/share/UbuntuLocationService/trust.db ~/.local/share/UbuntuLocationService/trust.db.bak
3. $ start ubuntu-location-service-trust-stored
4. launch webbrowser-app (it is unconfined)
5. navigate to maps.google.com. it will prompt to access location (browser prompt). Say yes
At this point I am presented with a trust session prompt:
"unconfined
An unconfined application wants to access your current location.
Deny
Allow"
6. tap 'Allow'
This adds the following to the trust store:
3|unconfined|0|1411758762544069109|1
location service shouldn't be prompting for this for the reasons
outlined above. Adding location-service task.
This will likely affect camera and mic in 'Other app access'.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1374577
Title:
'unconfined' should be precached and not listed under 'Location
access' (or 'Other app access')
Status in “location-service” package in Ubuntu:
New
Status in “ubuntu-system-settings” package in Ubuntu:
New
Bug description:
If I go to Location access under Security & Privacy, I have an entry
in the list that is blank which corresponds to 'unconfined'
('unconfined' should be precached to default to 'allow' anyway).
We should not prompt the user for unconfined or allow the user to
adjust entries for 'unconfined' processes in System Settings since
this might break things in unexpected ways. Marking as Critical and
for rtm14 because this is user facing, confusing to have a blank
entry, can lead to unexpected behavior, it should be trivial to filter
this out in system settings and because it should be easy to precache
this.
Steps to reproduce (this resets the location trust-store db):
1. $ stop ubuntu-location-service-trust-stored
2. mv ~/.local/share/UbuntuLocationService/trust.db ~/.local/share/UbuntuLocationService/trust.db.bak
3. $ start ubuntu-location-service-trust-stored
4. launch webbrowser-app (it is unconfined)
5. navigate to maps.google.com. it will prompt to access location (browser prompt). Say yes
At this point I am presented with a trust session prompt:
"unconfined
An unconfined application wants to access your current location.
Deny
Allow"
6. tap 'Allow'
This adds the following to the trust store:
3|unconfined|0|1411758762544069109|1
location service shouldn't be prompting for this for the reasons
outlined above. Adding location-service task.
This will likely affect camera and mic in 'Other app access'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1374577/+subscriptions