I would like to request the use of the costum-device interface for the snap sponge-controller.
- name: sponge-controller
- description: : Used for internal processes that require serial access
- snapcraft: PRIVATE
- upstream: PRIVATE
- upstream-relation: Publisher
- interfaces:
- custom-device:
- request-type: installation and connection
- reasoning: Accessing serial interfaces
/dev/ttyAMA0
and /dev/ttyAMA1
, possibly more in the future
See related topic: Classic Confinement Request for sponge-controller
1 Like
Hey @spongebas
custom-device
is considered super-privileged and publisher vetting is needed. When the upstream source code is private, the publisher is vetted through the Verified Accounts process.
Thanks
Hi @jslarraz.
Thanks for replying. Is a verified account also required for private/unlisted snaps?
I would like to get permissions to the serial ports sorted out sooner than later since its holding up the development of our project. Would it be faster to continue with the classic confinement request instead?
Thanks,
Hey @spongebas
Yes, it is also required for private/unlisted snaps as they can be made public with out any additional verification.
Publisher vetting is also required for classic confinement, so it would not be faster.
Thanks