Add support for socketpair() in the default profile

[Ted Gould]

Socketpair() can only be used for local sockets, so it should be allowed in the default profile and not require network-client or network-server.

[Jamie Strandboge (jdstrand)]

I agree QML apps should not require networking. For now I suggest an alternate approach from changing ubuntu-core-security policy as seen in this MP: https://code.launchpad.net/~jdstrand/mir/snappy-packaging.framework-policy-for-qml-apps/+merge/264439

[Ted Gould (ted)]

I guess my only question would be how often socketpair() is used. This
solves the Mir case of course, but I figured it was more widely used
than just Mir and kinda a standard Unix feature. For instance two
processes in the same application could use it to communicate with each
other (backend/frontend type architecture).

[Jamie Strandboge (jdstrand)]

I think this is a good point. It is fixed now in mir framework-policy, but we should allow it in default policy too.

[Jamie Strandboge (jdstrand)]

Uploaded to wily and https://launchpad.net/~snappy-dev/+archive/ubuntu/image/.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-core-security - 15.10.9

---------------
ubuntu-core-security (15.10.9) wily; urgency=medium

  * ubuntu-core/default, ubuntu-core/network-service: move socketpair from
    network-service policy group to default template since on Linux socketpair
    only supports AF_UNIX (LP: #1470995)
  * ubuntu-core/default: allow ixr of openssl (LP: #1480366)

 -- Jamie Strandboge <email address hidden> Fri, 31 Jul 2015 15:35:43 -0500