{"id":135,"date":"2011-05-26T22:47:32","date_gmt":"2011-05-27T05:47:32","guid":{"rendered":"http:\/\/blog.networkpresence.co\/?p=135"},"modified":"2011-05-27T05:47:39","modified_gmt":"2011-05-27T12:47:39","slug":"securing-tmp-other-linux-webhost-tightening-measures","status":"publish","type":"post","link":"http:\/\/blog.networkpresence.co\/?p=135","title":{"rendered":"Securing \/tmp & other Linux Webhost “tightening” measures"},"content":{"rendered":"

As per a post in our Forums, we’ve recently outlined how to get your Linux system a separate \/tmp filesystem<\/a>, which won’t allow executables and has other values to keep ‘nefarious’ content out of \/tmp<\/p>\n

In this post we outline some other simple things that can be done to stop “unwanted usage” of your web hosting Linux server.<\/p>\n

What’s “unwanted usage” mean, well basically anything that isn’t what you want your web server to do. In many cases, there are code vulnerabilities which can be exploited in common web hosting software like; PHP and other, which mean that crackers can try to find ways to get your web server to do things which you hadn’t intended (eg: IRC servers, hosting other content & more).<\/p>\n

Often PHP & other backend software system exploits are used to get your web host to download other software, install it & then run it. There are many conventional Linux commands which can be used to do this initial downloading, including commands like; wget, lynx, ftp (as a client) & more. But usually these commands are needed in the regular operation of a web server, so one solution is to stop the ability of the process running your web server (eg: the user apache or www on your web server) from accessing these commands. A simple way to do this is to remove the ‘other’ permission from the executables of these commands, like:
\nchmod o= \/usr\/bin\/wget
\nThen do the same for the ‘ftp’, ‘lynx’ & other Internet client commands.<\/p>\n

Of course, completely removing unnecessary software from your web server host is also a good thing to do & you can do that through your favourite Package Management system (eg: yum, apt, etc). eg: “yum remove wget” in the case of the wget utility.
\nIf you’re not sure what Package installed the relevant executable program and you’re using Yum, then “yum whatprovides ‘*\/wget'” would reveal the package name that installed the wget program to your Linux system.<\/p>\n

Another idea is to remove unnecessary scripting languages from being able to be accessed by the web server processes & user, so like above, remove the executable flag for the web server (or ‘other’) user from files like; the Python & Ruby executables (if they’re installed).<\/p>\n

Finally, as also mentioned in our Forums<\/a>, wherever possible, we recommend that customers keep their systems up to date with the latest available software versions & releases. In Redhat based Linux, this can be done with the Yum command, “yum upgrade”, and in Debian\/GNU Linux versions, if you’re using APT, the command, “apt-get upgrade”.
\nNaturally, if these upgrades install a new kernel version, you will probably need to update your Boot Loaders config for that new kernel release’s file. eg: \/boot\/grub\/grub.conf (Redhat based) or \/boot\/grub\/menu.lst (GNU Linux based)<\/p>\n

Don’t forget that we’re available to assist Network Presence customers<\/a> with any of these issues & actions, so please feel free to contact us.<\/p>\n","protected":false},"excerpt":{"rendered":"

As per a post in our Forums, we’ve recently outlined how to get your Linux system a separate \/tmp filesystem, which won’t allow executables and has other values to keep ‘nefarious’ content out of \/tmp In this post we outline … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[18,21],"class_list":["post-135","post","type-post","status-publish","format-standard","hentry","category-network-presence","tag-linux","tag-security"],"_links":{"self":[{"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=\/wp\/v2\/posts\/135","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=135"}],"version-history":[{"count":4,"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=\/wp\/v2\/posts\/135\/revisions"}],"predecessor-version":[{"id":148,"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=\/wp\/v2\/posts\/135\/revisions\/148"}],"wp:attachment":[{"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=135"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=135"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.networkpresence.co\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}