https://bugs.kde.org/show_bug.cgi?id=353874
--- Comment #25 from Méven <me...@kde.org> --- (In reply to Méven from comment #24) > (In reply to tagwerk19 from comment #23) > > (In reply to Méven from comment #22) > > > Baloo should be be able to fix this using fanotify > > > https://man7.org/linux/man-pages/man7/fanotify.7.html for any user with > > > linux 5.1+. > > I see a: > > Calling fanotify_init() requires the CAP_SYS_ADMIN capability. > > presumably meaning fanotify needs admin rights. > > It seems to me that's not what man fanotify documentation says. > The example does not make use of it either. > It mention fanotify should not be run with CAP_SYS_ADMIN or unprivileged > users would have access to more than they should. Sorry you are right https://man7.org/linux/man-pages/man2/fanotify_init.2.html The API does need CAP_SYS_ADMIN. So baloo could achieve this using an external root-owned with sticky bit exec whose only role would be to send to baloo files changes in index directories. -- You are receiving this mail because: You are watching all bug changes.
