Classic confinement request for prazycron

store-requests classic-confinement
1

  • name: prazycron

  • description: PrazyCron Task Manager provides graphical and terminal interfaces for managing Linux Cron jobs and systemd timers. It validates changes, creates backups, previews diffs, calculates future runs, records execution history, and diagnoses common scheduling problems.

  • snapcraft: prazycron/snap/snapcraft.yaml at main · Prazynka/prazycron · GitHub

  • upstream: GitHub - Prazynka/prazycron: A graphical and terminal manager for Linux Cron jobs and systemd timers. Cron made simple. · GitHub

  • upstream-relation: I am the upstream author and maintainer of PrazyCron, and I am also the publisher of this snap.

  • supported-category: PrazyCron does not map cleanly onto one of the currently listed supported categories. It is a host scheduling and system-administration tool. I am requesting a technical review based on the requirements described below.

  • reasoning: PrazyCron’s core purpose is to manage the host system’s actual scheduling facilities rather than a private scheduler contained inside the snap. It needs to:

    • read and modify the real user crontab through the host crontab command;
    • inspect and manage user and system systemd timers through the host systemctl command;
    • inspect execution information and logs from the host system;
    • access the host paths, scripts, executables, working directories, and environment referenced by scheduled jobs;
    • execute arbitrary user-configured commands and scripts in their normal host environment;
    • use PolicyKit authorization for operations involving system-wide Cron jobs and systemd timers.

Strict confinement interfaces cannot provide transparent access to arbitrary host executables, arbitrary paths referenced by existing scheduled tasks, the real host crontab environment, and unrestricted user/system systemd timer management. Restricting PrazyCron to the snap sandbox would remove its central functionality and would create schedules that do not behave like schedules created with the system’s native tools.

I understand that strict confinement is generally preferred over classic.

I have reviewed the existing interfaces, but they do not cover the combination of host crontab editing, systemd timer management, arbitrary user-defined command execution, and PolicyKit-authorized system operations required by PrazyCron.

2

This request has been added to the queue for review by the @reviewers team.