Request for classic confinement: checkbox-oem

[Sorry, I cannot put more than 2 links, so couldn’t link everything properly]

To make the review of your request easier, please use the following template to provide all the required details and also include any other information that may be relevant.


  • name: checkbox-oem
  • description: Checkbox provider for OEM integration testing
  • snapcraft: checkbox/contrib/checkbox-oem/checkbox-oem-snap/series_classic26/snap/snapcraft.yaml at checkbox-oem_pc-sanity · sampaio23/checkbox · GitHub, to be merged to checkbox upstream repo
  • upstream: same as above, to be merged to checkbox upstream repo
  • upstream-relation: I am the publisher and the upstream maintainer
  • supported-category: debug tools (based on previous case request-classic-confinement-for-checkbox-laramie-classic/49381)
  • reasoning: we aim to adopt the custom frontend interface, but some existing projects are still using the previous design; we plan to introduce it for Core 26. For classic 26.04, there are some issues to be resolved by QA team. See this PR

I understand that strict confinement is generally preferred over classic.

I’ve tried the existing interfaces to make the snap to work under strict confinement. - As mentioned above, the custom-frontend interface can and should be used, but QA has to fix several issues first.

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

Sure, the similar request has benn granted inthe past:

https://forum.snapcraft.io/t/request-for-classic-confinement-with-checkbox-test-provider-for-tdx-testing/43382

https://forum.snapcraft.io/t/auto-review-for-checkbox-koto-classic/45382

So it will be good in this case, publisher is already vetted and a canonical employee. This is now live