Request classic confinement for ssd-tester

store-requests classic-confinement
1

name: ssd-tester

description: SSD-Tester App is a desktop SSD benchmark and storage diagnostics application for NVMe, SATA, and USB storage devices.

snapcraft: PRIVATE

upstream: PRIVATE

upstream-relation: The snap is published and maintained by the upstream project author.

supported-category: debug tools

reasoning: The application performs user-initiated storage diagnostics, including reading SMART/NVMe data, starting device self-tests, error scans, capacity verification, TRIM checks, and secure erase operations.

The current implementation requires direct access to raw block devices and elevates selected operations using pkexec or sudo. I understand that strict confinement is generally preferred. I have reviewed the available interfaces, including block-devices, which provides privileged raw block-device access and requires a Store declaration.

The current snap has not yet been redesigned to use strict confinement and block-devices exclusively. I am requesting guidance on whether the required diagnostics can be supported through that interface, or whether classic confinement is appropriate for this snap.

More Infos: https://ssd-tester.com/app_download.php

2

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

3

Hi @ssd-tester,

For the functionality of the snap, direct access to raw block devices should suffice instead of classic.

Also note that block-device is a privileged interface and will need a separate forum post and approval from reviewers. To test the functionality locally before uploading to the store, you should be able to install a local snap with –dangerous flag. e.g. sudo snap install /path/to/package.snap --dangerous

As per Process for reviewing classic confinement snaps, direct access to pkexec and sudo, comes under unsupported categories.

Considering both of the reasons, I am unable to grant classic for ssd-tester.