When you plan to run git-http-backend (which might be a part of Zuul's setup in your CI/CD) along side with Nginx and fastcgi, ensure to put there a proper config in the location, to avoid errors like:
It is very common these days, when a vulnerable website gets exploited and used for malicious activities by attackers. Especially when having a "shared hosting" environment you may get used to discovering a new kind of malware on a daily basis. Here I'm going to present one of these tools, which is worth using in that malware hunting.
When renting a dedicated server usually we get the whole net block of ipv6 addressess in a "package", along with just one or few IPv4 routable address. Having ipv6'es is nice and would be even better to make use of these, especially when IPv6 should not electricize anyone these days. In this post I''ll present a case, how to get workin' ip6 network on a guest virtual machine, which configuration is handled by libvirt(d), using the native v6 address from our rented net block.
Any web application can have a security bug, which exploited, may allow the attacker to gain unauthorized access to crucial application components, and, unfortunately, lead to a leakage of a sensitive data. One of the common ways to defend the zero days is to use WAF (Web Application Firewall). In this tutorial I'll put some light on a dedicated Nginx WAF external module called NAXSI (Nginx Anti XSS & SQL Injection), the ModSecurity equivalent for Apachers, by the way...