From 96bed5ca62fbee6cfc7e69a473ab300c78e9ad9d Mon Sep 17 00:00:00 2001 From: Michal Date: Mon, 30 Mar 2020 19:17:02 +0200 Subject: [PATCH] update non-root-user.polish.md fixed, just a typo --- sections/security/non-root-user.polish.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sections/security/non-root-user.polish.md b/sections/security/non-root-user.polish.md index 6ad823c6..c77fc91b 100644 --- a/sections/security/non-root-user.polish.md +++ b/sections/security/non-root-user.polish.md @@ -37,5 +37,5 @@ Z bloga Don't run Node.js as root od [Olivier Lalonde](http://syskall.com/dont-r ### Cytat z Blogu: "If you need to run your application on port 80 or 443, you can do port forwarding" -Z blogu Developing Secure Node.js Applications — A Broad Guide by [Deepal Jayasekara](https://jsblog.insiderattack.net/developing-secure-node-js-applications-a-broad-guide-286afdec69ce): +Z bloga Developing Secure Node.js Applications — A Broad Guide by [Deepal Jayasekara](https://jsblog.insiderattack.net/developing-secure-node-js-applications-a-broad-guide-286afdec69ce): > Never run Node.js as root. Running node.js as root will make it worse if an attacker somehow gains control over your application. In this scenario, attacker would also gain root privileges which could result in a catastrophe. If you need to run your application on port 80 or 443, you can do port forwarding using iptables or you can place a front-end proxy such as nginx or apache which routes request from port 80 or 443 to your application