summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/secure_chroot.mdwn
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-03-12 08:18:17 +0100
committerantrik <antrik@users.sf.net>2009-03-12 09:17:12 +0100
commit3f98ec59e0c6287c50cbe34d5df8e69ffd28d754 (patch)
tree61fdd05d440bf434ff95f65acc3f542cdbdbb61f /community/gsoc/project_ideas/secure_chroot.mdwn
parentf7fbc506eaa66c6e17d12b9d2c2618c877937ddc (diff)
secure chroot GSoC task: Add links to ideas/discussions
Diffstat (limited to 'community/gsoc/project_ideas/secure_chroot.mdwn')
-rw-r--r--community/gsoc/project_ideas/secure_chroot.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/community/gsoc/project_ideas/secure_chroot.mdwn b/community/gsoc/project_ideas/secure_chroot.mdwn
index f091527a..f5c744e2 100644
--- a/community/gsoc/project_ideas/secure_chroot.mdwn
+++ b/community/gsoc/project_ideas/secure_chroot.mdwn
@@ -23,6 +23,11 @@ translator mechanism. Some involving a completely different approch to
`chroot` implementation, using a proxy instead of a special system call in the
filesystem servers.
+See <http://tri-ceps.blogspot.com/2007/07/theory-of-filesystem-relativity.html>
+for some suggestions, as well as the followup discussions on
+<http://lists.gnu.org/archive/html/gnu-system-discuss/2007-09/msg00118.html>
+and <http://lists.gnu.org/archive/html/bug-hurd/2008-03/msg00089.html>.
+
The task is to pick and implement one approach for fixing chroot.
This task is pretty heavy: it requires a very good understanding of file name