summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas
diff options
context:
space:
mode:
authorantrik <antrik@users.sf.net>2009-03-12 07:51:13 +0100
committerantrik <antrik@users.sf.net>2009-03-12 09:17:11 +0100
commitf7fbc506eaa66c6e17d12b9d2c2618c877937ddc (patch)
tree32ec718a2a0ca09bf0fffebb8bafc0027dc79e80 /community/gsoc/project_ideas
parent7ef4852a9ade5f8b3932c9942170431699fada77 (diff)
secure chroot GSoC task: Fix typo
Diffstat (limited to 'community/gsoc/project_ideas')
-rw-r--r--community/gsoc/project_ideas/secure_chroot.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/secure_chroot.mdwn b/community/gsoc/project_ideas/secure_chroot.mdwn
index a47bd5db..f091527a 100644
--- a/community/gsoc/project_ideas/secure_chroot.mdwn
+++ b/community/gsoc/project_ideas/secure_chroot.mdwn
@@ -29,7 +29,7 @@ This task is pretty heavy: it requires a very good understanding of file name
lookup and the translator mechanism, as well as of security concerns in general
-- the student must prove that he really understands security implications of
the UNIX namespace approach, and how they are affected by the introduction of
-new mechanisms. (Translators.) More important than the acualy code is the
+new mechanisms. (Translators.) More important than the actual code is the
documentation of what he did: he must be able to defend why he chose a certain
approach, and explain why he believes this approach really secure.