lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-215676-13602@https.bugzilla.kernel.org/>
Date:   Sat, 12 Mar 2022 11:19:16 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 215676] New: fanotify Ignoring/Excluding a Directory not
 working with FAN_MARK_MOUNT

https://bugzilla.kernel.org/show_bug.cgi?id=215676

            Bug ID: 215676
           Summary: fanotify Ignoring/Excluding a Directory not working
                    with FAN_MARK_MOUNT
           Product: File System
           Version: 2.5
    Kernel Version: 5.11.0-27
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: talkwithsrinivas@...oo.co.in
        Regression: No

Created attachment 300557
  --> https://bugzilla.kernel.org/attachment.cgi?id=300557&action=edit
Test program to show directory exclusion not working

If a  process calls fanotify_mark(fd, FAN_MARK_ADD | FAN_MARK_MOUNT,
FAN_OPEN_PERM, 0, "/mountpoint") no other directory exclusions can be applied.

However a path (file) exclusion can still be applied using 

fanotify_mark(fd, FAN_MARK_ADD | FAN_MARK_IGNORED_MASK |
FAN_MARK_IGNORED_SURV_MODIFY, FAN_OPEN_PERM | FAN_CLOSE_WRITE, AT_FDCWD,
"/tmp/fio/abc");  ===> path exclusion that works.


I think the directory exclusion not working is a bug as otherwise AV solutions
cant exclude directories when using FAN_MARK_MOUNT.

I believe the change should be simple since we are already supporting path
exclusions. So we should be able to add the same for the directory inode.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ