Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1251716 > unrolled thread

Bug#1108691: pmount silently skips fstype autodetect with blkid when ran not by root

Started byNikolas Kyx <knv418@gmail.com>
First post2025-07-03 09:20 +0200
Last post2025-07-04 09:50 +0200
Articles 2 — 1 participant

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1108691: pmount silently skips fstype autodetect with blkid when ran not by root Nikolas Kyx <knv418@gmail.com> - 2025-07-03 09:20 +0200
    Bug#1108691: pmount silently skips fstype autodetect with blkid when ran not by root Nikolas Kyx <knv418@gmail.com> - 2025-07-04 09:50 +0200

#1251716 — Bug#1108691: pmount silently skips fstype autodetect with blkid when ran not by root

FromNikolas Kyx <knv418@gmail.com>
Date2025-07-03 09:20 +0200
SubjectBug#1108691: pmount silently skips fstype autodetect with blkid when ran not by root
Message-ID<L4moF-eTKh-1@gated-at.bofh.it>
Package: pmount
Version: 0.9.23-9
Severity: normal

1) Mount smth with command /usr/bin/pmount --debug PART
2) Look at pmount output and see no evidence of HAVE_BLKID code executed
3) Check ldd and package dependency and indeed there is libblkid
4) Look at the HAVE_BLKID code in src/pmount.c. Suspect that
tp = blkid_get_tag_value(c, "TYPE", device) is NULL.
pmount don't have a message for this case, sadly.
5) Now run (already SUID) /usr/bin/pmount --debug as root (e.g. with
sudo) and see that:
> blkid gave FS vfat for '/dev/sdb1'

Interesting why tp is NULL in SUID case but not NULL when run as root.
Tried with ext4 and vfat/fat32 partitions.
lsblk -f detects fs types both without sudo and suid.

[toc] | [next] | [standalone]


#1251803

FromNikolas Kyx <knv418@gmail.com>
Date2025-07-04 09:50 +0200
Message-ID<L4Jlf-f8jT-1@gated-at.bofh.it>
In reply to#1251716
It looks like openat() syscall is failing with EACCESS somewhere in
the blkid_get_tag_value(). So get_root() is needed to run this
function. Not sure whether it's safe.

lsblk implements a whole internal library to gather info about block
devices, it supports multiple data gathering methods (e.g. from udev).
So lsblk-way is not applicable here :(

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web