Classic confinement request for gallic-netbooster

store-requests
1

To make the review of your request easier, please place it in the appropriate subcategory (classic-confinement, privileged-interfaces, aliases, tracks, transfer-ownership or guardrail). You can use the dropdown menu to choose the subcategory as shown in the following image:

Hello,

I have uploaded the first revision of my snap, gallic-netbooster, and it is currently pending manual review due to classic confinement.

This application is a VPN utility. It requires classic confinement because it needs to interact directly with the host system’s networking stack to create virtual network interfaces (TUN/TAP devices), modify system routing tables, and manage global network traffic safely and reliably.

Could a reviewer please look into this request?

Thank you, Kondwani

2

This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.

3

There are plenty of strictly confined VPN clients in the store already all utilizing the respective interfaces to have full control over the hosts network stack, there bis no need for classic confinement for this use case …

Also please see the criteria a snap must fulfill to be considered for classic confinement:

Reviewing classic confinement snaps - Snap documentation (especially the “supported” and “unsupported” categories)

I would suggest you take a look at how the other VPN clients do this by utilizing the network-setup-control, network-control and firewall-control interfaces …