<div dir="ltr">Hi,<div>I agree with Alan.</div><div>Some other snaps that could need something like this could be app launchers (e.g. Whisker Menu) and desktop environments.</div><div><br></div><div>Cheers</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 September 2016 at 12:58, Alan Pope <span dir="ltr"><<a href="mailto:alan.pope@canonical.com" target="_blank">alan.pope@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
This is an architectural snappy question where I have one use case,<br>
but have seen others mention similar issues which may be related.<br>
Perhaps they could speak up also with their requirements.<br>
<br>
With regards to<br>
<a href="https://code.launchpad.net/~popey/ubuntu-terminal-app/add-snapcraft-config/+merge/305206" rel="noreferrer" target="_blank">https://code.launchpad.net/~<wbr>popey/ubuntu-terminal-app/add-<wbr>snapcraft-config/+merge/305206</a><br>
<br>
<a href="http://people.canonical.com/~alan/ubuntu-terminal-app_0.7.207_amd64.snap" rel="noreferrer" target="_blank">http://people.canonical.com/~<wbr>alan/ubuntu-terminal-app_0.7.<wbr>207_amd64.snap</a><br>
<br>
I made the above merge and snap to test out the phone terminal app on<br>
the desktop as a snap, for possible inclusion in the store. The goal<br>
being that people can install it on a Unity8 snap-only system.<br>
<br>
But, it's a bit useless in its current form, due in part to our<br>
confinement and store policies. In the click store (on the phone) the<br>
app is unconfined, so can access files/programs outside of the click.<br>
<br>
If I set confinement to be 'strict' then I can put it in the stable<br>
store, but you can't actually run any non-built-in things (like ssh,<br>
top), making it unusable for most people.<br>
<br>
If I make it use the 'devmode' confinement policy then it (as I<br>
understand it) *cannot* go into the stable store (by policy), but can<br>
execute external commands in the core. However, it can't be used to<br>
launch other executables in other snaps, making it somewhat useless on<br>
a snap-only system with other tools installed.<br>
<br>
I don't believe this to be unique to this terminal, nor<br>
desktop/graphical apps, other snap-packaged terminals (and file<br>
managers & other system level things) may have the same issue.<br>
<br>
How do we we resolve this? Do we request a security exception & code audit?<br>
Is there some other planned interface for these kinds of 'expert' apps<br>
which need to reach outside of their confinement?<br>
<br>
Cheers,<br>
<span class="HOEnZb"><font color="#888888">--<br>
Alan Pope<br>
Community Manager<br>
<br>
Canonical - Ubuntu Engineering and Services<br>
<a href="tel:%2B44%20%280%29%207973%20620%20164" value="+447973620164">+44 (0) 7973 620 164</a><br>
<a href="mailto:alan.pope@canonical.com">alan.pope@canonical.com</a><br>
<a href="http://ubuntu.com/" rel="noreferrer" target="_blank">http://ubuntu.com/</a><br>
<br>
--<br>
Snapcraft mailing list<br>
<a href="mailto:Snapcraft@lists.snapcraft.io">Snapcraft@lists.snapcraft.io</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/<wbr>mailman/listinfo/snapcraft</a><br>
</font></span></blockquote></div><br></div>