Setting up access to packages GUI in System - User Manager


  • Banned

    Packages supported so far:

    • arping

    • arpwatch

    • avahi

    • backup

    • bacula-client

    • bandwidthd

    • blinkled

    • checkmk-agent

    • cron

    • darkstat

    • diag_new_states

    • filemgr

    • filer

    • ftpproxy

    • gwled

    • lightsquid

    • sarg

    • squid3

    • sshdcond

    • stunnel

    • sudo

    • syslog-ng

    • tftp

    • tinc

    • vhosts

    • widentd

    • zabbix2-agent/zabbix2-proxy

    • zabbix-agent-lts/zabbix-proxy-lts

    • of course those that already supported this feature before:
    • asterisk

    • pfBlockerNG

    • Snort

    • Suricata

    • System Patches

    The location in the ACL list conforms to the location where the package menu entry is placed. So, if you have say Diagnostics - ARPing, the ACL is listed as WebCfg: Diagnostics: ARPing package in System - User Manager - Add privileges.

    Note: If you want those to have any effect, do NOT grant the users with access to WebCfg - Package: Edit page and/or WebCfg - Package: Settings page. That will render any of those package-specific privileges ineffective and provide access the user with access to all packages.


  • Banned

    Added to bunch of other packages, updated list in the first post.


  • Banned

    Should be almost complete now, added to ~30 other packages. There are some ~10 packages remaining.


Log in to reply