we need access to the mac address for our licensing.
We call a subprogram which executes “ip link show“ to achieve that.
So our smart-sip-phone needs the network-observe interface.
name: smart-sip-phone
description: SIP client for every SIP telephone system
upstream: PRIVATE
upstream-relation: we are the developers and maintainers of the client
interfaces:
network-observe:
request-type: auto-connection
reasoning: we need access to the mac address for our licensing.
We call a subprogram which executes “ip link show“ to achieve that.
So our smart-sip-phone needs the network-observe interface.
Since you need the network-observe interface , just for MAC-address retrieval, it might be a stretch to grant auto-connection, as it gives an application wide-ranging visibility into the host’s network status, routing tables, and socket activity.
I am thinking that maybe manual-connection is a better idea. This means your snap will install, but users (or your deployment scripts) will need to run a command post-installation to grant the permission:
The problem is, it is not optional (and manual-connection can fail), because without mac address a user cant activate a purchased pro license. This would be very frustrating for the users.
On another note, we previously requested auto-connection for the pipewire interface, and it was granted at the time.
However, due to a high workload over the past few months, we were not able to upload a new version that actually uses the interface. As a result, the auto-connection has not been enabled for our snap yet.
Would it still be possible to enable the previously granted auto-connection after this delay, or should we submit a new request?
