Hi,
I’m Luca, the developer and maintainer of Portop.
I’m currently working on distributing Portop as a strictly confined Snap and I’m requesting auto-connection for the interfaces listed below, as they are required for the application’s core functionality.
name: portop
description: | Portop is an htop-style terminal UI for inspecting network ports and their associated processes, systemd units and Docker containers. It also allows users to terminate a selected process directly from the TUI.
snapcraft: Not publicly available yet. The snapcraft.yaml is currently maintained separately while the Snap packaging is being validated and will be added to the upstream repository once finalized.
upstream-relation: I am the upstream developer, maintainer and Snap Store publisher.
plugs: network-observe: request-type: auto-connection reasoning: | Portop’s primary purpose is inspecting the host’s network sockets and displaying TCP/UDP ports and connections. Access to network information is core functionality of the application.
system-observe: request-type: auto-connection reasoning: | Portop associates network sockets with the processes that own them and displays process information including PID, command line, user, memory usage, threads and associated systemd units. Host process inspection is core functionality of Portop.
process-control: request-type: auto-connection reasoning: | Portop provides an explicit interactive action that allows the user to terminate the process associated with a selected network socket. Process termination is performed only following an explicit user action from the TUI and Portop never terminates processes automatically.
slots: {}
Additional information
Portop is open source and licensed under the MIT license:
The snap uses strict confinement.
Version 0.1.0, revision 2, is currently available in latest/edge:
sudo snap install portop --edge
Snap Store ID:
hbkQUgszmsaQVko2R4VFNINsnmKCNhBU
I have tested the strictly confined snap with all three requested interfaces manually connected. Network inspection, process information, systemd information and process control work correctly.
Portop 0.1.0 also introduces a web dashboard. The dashboard uses the standard
network-bind interface, which is automatically connected and therefore is not
part of this auto-connect request.
After a normal installation from the Store, the following requested interfaces are currently left disconnected and have to be connected manually by the user:
sudo snap connect portop:network-observe
sudo snap connect portop:system-observe
sudo snap connect portop:process-control
Thanks for reviewing the request.
