From afede536ae60f6886226063577e9384c077a0638 Mon Sep 17 00:00:00 2001 From: a-maze-d Date: Thu, 22 Jun 2017 14:23:44 +0200 Subject: [PATCH] Fixing broken link The link for "Understanding and Hardening Linux Containers" was broken, since the document was updated (v1.1 instead of v1.0) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c55bb72..9bb9a7a 100644 --- a/README.md +++ b/README.md @@ -489,7 +489,7 @@ First things first: Docker runs as root. If you are in the `docker` group, you e Docker should not be your only defense. You should secure and harden it. -For an understanding of what containers leave exposed, you should read is [Understanding and Hardening Linux Containers](https://www.nccgroup.trust/globalassets/our-research/us/whitepapers/2016/april/ncc_group_understanding_hardening_linux_containers-10pdf) by [Aaron Grattafiori](https://twitter.com/dyn___). This is a complete and comprehensive guide to the issues involved with containers, with a plethora of links and footnotes leading on to yet more useful content. The security tips following are useful if you've already hardened containers in the past, but are not a substitute for understanding. +For an understanding of what containers leave exposed, you should read is [Understanding and Hardening Linux Containers](https://www.nccgroup.trust/globalassets/our-research/us/whitepapers/2016/april/ncc_group_understanding_hardening_linux_containers-1-1.pdf) by [Aaron Grattafiori](https://twitter.com/dyn___). This is a complete and comprehensive guide to the issues involved with containers, with a plethora of links and footnotes leading on to yet more useful content. The security tips following are useful if you've already hardened containers in the past, but are not a substitute for understanding. ### Security Tips