Feature #5367
wheezy: adapt persistence of NM connections
0%
Description
Persistence for NM connections is broken. See corresponding issue in Liberte
Is it really, even after most of the secrets handling was moved back to GNOME keyring, and the Wi-Fi connections back to be considered as "user" ones unless user is allowed to configure system ones (since network-manager-gnome 0.9.4.1-3)? Perhaps tweaking the policykit settings so that the
amnesia
user is not allowed to configure connections would be enough to workaround this?
Subtasks
History
#1 Updated by Tails 2013-07-18 10:34:30
- Parent task set to
Feature #6015
#2 Updated by intrigeri 2013-10-04 08:55:10
- Subject changed from wheezy: persistence for nm connections is broken to wheezy: persistence of NM connections is broken
- Starter set to No
#3 Updated by intrigeri 2013-12-08 14:44:21
- Assignee set to intrigeri
#4 Updated by intrigeri 2013-12-08 14:46:52
- Target version set to Tails_1.1
#5 Updated by intrigeri 2013-12-08 14:53:23
- Target version deleted (
Tails_1.1)
#6 Updated by intrigeri 2013-12-08 16:19:43
- Target version set to Tails_1.1
#7 Updated by intrigeri 2013-12-22 07:26:36
tails-persistence-setup 1.0.2-1+wheezy1 adapts the persistent path for Wheezy. My understanding of the Debian changelog wrt. 11-user-connections.patch
is that all relevant passwords should still be stored in GNOME keyring, so it should presumably all work as before. Should be tested, though.
#8 Updated by intrigeri 2013-12-22 07:34:36
- Subject changed from wheezy: persistence of NM connections is broken to wheezy: adapt persistence of NM connections
#9 Updated by intrigeri 2013-12-23 07:45:19
- Status changed from Confirmed to Resolved
- Type of work changed from Research to Code
Now works just fine.