From: tornaria <firstname.lastname@example.org>
Subject: Re: [PR REVIEW] libmtp: update to 1.1.19.
Date: Sun, 27 Feb 2022 18:38:23 +0100 [thread overview]
Message-ID: <20220227173823.1NJjCKk62idC8de0KJnvXiMYmOD2oYEQIifSCbBAxfQ@z> (raw)
[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]
New review comment by tornaria on void-packages repository
> so libmtp is broken on all the other distros then?
I don't know, I don't use other distros. Is there a different method to give users access to usb devices? The only methods that come to my mind are: (a) make the device group-readable by a well known group (b) run the programs that need to access the device as root (either setuid or sudo) (c) have a daemon running as root that the programs talk to. I don't think libmtp has (c) and (b) seems unsafe so (a) is the only reasonable choice AFAICT.
> i would go with what gentoo does (`plugdev`), as that's used in some templates already
- `plugdev` is not documented here: https://docs.voidlinux.org/config/users-and-groups.html#default-groups
- I see three packages create group `plugdev`, namely `openocd`, `openrazer-meta` and `wally-udev-rules`, so maybe it's ok to use `plugdev` without underscore (the policy says to use underscore: "System accounts and groups must be prefixed with an underscore to prevent clashing with names of user accounts." except for old packages).
- debian says `plugdev` "Allows members to mount (only with the options nodev and nosuid, for security reasons) and umount removable devices through pmount." (https://wiki.debian.org/SystemGroups)
- in void pmount is setuid root instead.
My rationale for `_libmtp` was that it is unambiguous what you are getting access to.
next prev parent reply other threads:[~2022-02-27 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 21:42 [PR PATCH] " tornaria
2022-01-04 8:01 ` [PR REVIEW] " ericonr
2022-01-05 1:15 ` tornaria
2022-01-20 13:21 ` tornaria
2022-02-25 21:55 ` Piraty
2022-02-25 21:57 ` Piraty
2022-02-25 22:03 ` tornaria
2022-02-25 22:15 ` tornaria
2022-02-25 23:08 ` Piraty
2022-02-26 0:32 ` Piraty
2022-02-26 13:35 ` tornaria
2022-02-26 21:58 ` Piraty
2022-02-27 17:38 ` tornaria [this message]
2022-03-19 23:07 ` [PR PATCH] [Updated] " tornaria
2022-03-19 23:10 ` [PR REVIEW] " tornaria
2022-03-19 23:12 ` tornaria
2022-04-06 22:53 ` 0x5c
2022-04-10 20:42 ` libmtp: update to 1.1.19, use plugdev group for r/w access to mtp devices tornaria
2022-04-10 23:39 ` [PR PATCH] [Merged]: " q66
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).