summaryrefslogtreecommitdiff
path: root/Kernel/Devices/ZeroDevice.h
diff options
context:
space:
mode:
authorLiav A <liavalb@gmail.com>2022-12-02 11:33:57 +0200
committerAndrew Kaster <andrewdkaster@gmail.com>2022-12-09 23:09:00 -0700
commitd4b65f644e17923290376e782aa31d51d5fc13f5 (patch)
treed907df94ce39b88a0f167fe1a69108a55dd1a5e9 /Kernel/Devices/ZeroDevice.h
parent968e1a6efc4041db2cc0489e99797bc0231392af (diff)
downloadserenity-d4b65f644e17923290376e782aa31d51d5fc13f5.zip
Kernel: Allow opening some device nodes sparingly for jailed processes
From now on, we don't allow jailed processes to open all device nodes in /dev, but only allow jailed processes to open /dev/full, /dev/zero, /dev/null, and various TTY and PTY devices (and not including virtual consoles) so we basically restrict applications to what they can do when they are in jail. The motivation for this type of restriction is to ensure that even if a remote code execution occurred, the damage that can be done is very small. We also don't restrict reading and writing on device nodes that were already opened, because that limit seems not useful, especially in the case where we do want to provide an OpenFileDescription to such device but nothing further than that.
Diffstat (limited to 'Kernel/Devices/ZeroDevice.h')
-rw-r--r--Kernel/Devices/ZeroDevice.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/Kernel/Devices/ZeroDevice.h b/Kernel/Devices/ZeroDevice.h
index 77c9f08e57..c539d4f048 100644
--- a/Kernel/Devices/ZeroDevice.h
+++ b/Kernel/Devices/ZeroDevice.h
@@ -20,6 +20,9 @@ public:
private:
ZeroDevice();
+ // ^Device
+ virtual bool is_openable_by_jailed_processes() const override { return true; }
+
// ^CharacterDevice
virtual ErrorOr<size_t> read(OpenFileDescription&, u64, UserOrKernelBuffer&, size_t) override;
virtual ErrorOr<size_t> write(OpenFileDescription&, u64, UserOrKernelBuffer const&, size_t) override;