summaryrefslogtreecommitdiffstats
path: root/usr.sbin/usbdump
diff options
context:
space:
mode:
authorpjd <pjd@FreeBSD.org>2011-05-31 07:02:49 +0000
committerpjd <pjd@FreeBSD.org>2011-05-31 07:02:49 +0000
commitb6ae7ca260605f046bb9ed7abc1beba20f7650a7 (patch)
treeabd41fb961a7db052213bb537207a2c1beb0797c /usr.sbin/usbdump
parent2adafc03232464837b5248397590e850ab6d7dc7 (diff)
downloadFreeBSD-src-b6ae7ca260605f046bb9ed7abc1beba20f7650a7.zip
FreeBSD-src-b6ae7ca260605f046bb9ed7abc1beba20f7650a7.tar.gz
Imagine situation where a security problem is found in setuid binary.
User upgrades his system to fix the problem, but if he has any ZFS snapshots for the file system which contains problematic binary, any user can mount the snapshot and execute vulnerable binary. Prevent this from happening by always mounting snapshots with setuid turned off. MFC after: 2 weeks
Diffstat (limited to 'usr.sbin/usbdump')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud