aboutsummaryrefslogtreecommitdiff
path: root/SECURITY.md
diff options
context:
space:
mode:
authorMiquel Sabaté Solà <mikisabate@gmail.com>2024-11-25 21:22:48 +0100
committerMiquel Sabaté Solà <mikisabate@gmail.com>2024-11-25 21:22:48 +0100
commit226c5c2e070b9831e3cbc81e9894b8048f8a932d (patch)
tree0c698229c9a76b29fc5e5d6cfc27f3162caf7595 /SECURITY.md
parent816044987ec4fbee3b88e04aabcf0a2edf83f908 (diff)
downloadfbos-226c5c2e070b9831e3cbc81e9894b8048f8a932d.tar.gz
fbos-226c5c2e070b9831e3cbc81e9894b8048f8a932d.zip
Add files for contributing to the project
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
Diffstat (limited to 'SECURITY.md')
-rw-r--r--SECURITY.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000..38e74d4
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,15 @@
+# Security Policy
+
+This is not a serious kernel, and hence we do not have any serious security
+policy. There are of course many things that could compromise a toy kernel such
+as this. For example:
+
+- Bad bound checks that could turn into a vector of attacks.
+- Bad enforcements of memory protection.
+ - Remember that this kernel does not implement any memory protection on the
+ purpose of being simple, but we could always enable other mechanisms to keep
+ things "secure".
+- Other kind of bugs that could compromise such as kernel.
+
+For any of these situations, since this is a toy project, simply submit an
+[issue to the Github repository](https://github.com/mssola/fbos/issues).