Public bug reported:

Running snapd on PureOS 8.0 (rolling release ~= Debian main testing). A recent 
update:
* upgraded to Linux kernel 4.13
* enabled AppArmor

Since then I can no longer `snap run packagename`. I get the following
error:

snap-confine has elevated permissions and is not confined but should be.
Refusing to continue to avoid permission escalation attacks

This has been reported on other non-Ubuntu distros:

* https://askubuntu.com/questions/888497
* https://unix.stackexchange.com/questions/379421

Could this be related to
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1682023 ?

Please advise if this should be addressed downstream.

** Affects: snapd (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Running snapd on PureOS 8.0 (rolling release ~= Debian main testing). A 
recent update:
- * upgrading to Linux kernel 4.13
+ * upgraded to Linux kernel 4.13
  * enabled AppArmor
  
  Since then I can't `snap run packagename`. I get the following error:
  
  snap-confine has elevated permissions and is not confined but should be.
  Refusing to continue to avoid permission escalation attacks
  
  This has been reported on other non-Ubuntu distros:
  
  * https://askubuntu.com/questions/888497
  * https://unix.stackexchange.com/questions/379421
  
  Could this be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1682023 ?

** Description changed:

  Running snapd on PureOS 8.0 (rolling release ~= Debian main testing). A 
recent update:
  * upgraded to Linux kernel 4.13
  * enabled AppArmor
  
- Since then I can't `snap run packagename`. I get the following error:
+ Since then I can no longer `snap run packagename`. I get the following
+ error:
  
  snap-confine has elevated permissions and is not confined but should be.
  Refusing to continue to avoid permission escalation attacks
  
  This has been reported on other non-Ubuntu distros:
  
  * https://askubuntu.com/questions/888497
  * https://unix.stackexchange.com/questions/379421
  
  Could this be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1682023 ?

** Description changed:

  Running snapd on PureOS 8.0 (rolling release ~= Debian main testing). A 
recent update:
  * upgraded to Linux kernel 4.13
  * enabled AppArmor
  
  Since then I can no longer `snap run packagename`. I get the following
  error:
  
  snap-confine has elevated permissions and is not confined but should be.
  Refusing to continue to avoid permission escalation attacks
  
  This has been reported on other non-Ubuntu distros:
  
  * https://askubuntu.com/questions/888497
  * https://unix.stackexchange.com/questions/379421
  
  Could this be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1682023 ?
+ 
+ Please advise if this should be addressed downstream.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732409

Title:
  snap-confine has elevated permissions and is not confined but should
  be

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1732409/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to