Dotdeb’s packages of Nginx 1.0.14 for Debian 6.0 “Squeeze” (amd64/i386) have been synchronized with Debian’s ones to benefit from the great work of Cyril Lavier.
As a consequence, two new flavors of Nginx are now available, in addition to the regular nginx-light, nginx-full and nginx-extras packages :
nginx-naxsiinherits fromnginx-lightwith a great new feature : Naxsi, a high performance, low rules maintenance, Web Application Firewall module. Use it if you want to protect your web apps from malicious visitors. Please read its documentation fore more info.nginx-passengeris dedicated to Passenger, the well-known Ruby on Rails runtime. Please also note that :- the
passenger-commonpackage has been renamed toruby-passengerto stick to the Debian naming convention, - Passenger was already included in
nginx-extras. To ease the migration (don’t forget to backup your configuration files), it will stay so until Nginx 1.2 is released.
- the
If you want to know which module has been included in each Nginx flavor, you just have to look at this useful document.
Oh… One more thing : all the Nginx packages are now hardened against memory corruption attacks (no PIE support yet).
I really hope you’ll enjoy them. And many thanks to the Debian maintainers for their work, of course.
again sorry ;d i had to kill nginx seems it didnt want to stop after kill and start i dont have that limit_req_zone error anymore
anyway about naxsi in extras when i uncomment naxi config it says “Starting nginx: nginx: [emerg] unknown directive “MainRule” in /etc/nginx/naxsi_core.rules:13 nginx: configuration file /etc/nginx/nginx.conf test failed”
so i guess google document says right ;)
@Matic : the goal for a WAF is to be as light as possible. Including naxsi in nginx-passenger would make no sense. It’s only available in nginx-naxsi.
@hanti : naxsi rules files belog to nginx-common, that is common to all the nginx flavors. Just ignore them (leave the naxsi-related directives commented if you don’t use nginx-naxsi). When you change the installed nginx flavor, a restart is often needed. It’s safer than the usual soft restart.
And of course, the Google doc says right :)
It’s the first time I post here so I want first to thank you for the incredible job you do here.
About nxasi, I was thinking to compile nginx in order to use it. That’s very good news. My only pb is that I use nginx-full. Is there any reason why nxasi is only available for nginx-light package ? Do you think you will release in the next weeks a nxasi version of nginx-full ?
Thanks a lot.
I have read the doc on google docs and discovered that http stub status module is integrated in nginx-light.
That’s perfect ! I can use nginx-naxsi now :)
@Guillaume Plessis : I don’t understand why you say a WAF has to be as light as possible. What about people using Nginx as a web server and not only as a proxy in front of Apache ?
Anyway, the best solution is to code correctly and not using stuff like WAF.
Getting the error in /var/log/ngnix/error.log
/usr/share/phusion-passenger/helper-scripts/passenger-spawn-server:75:in `require’: no such file to load — rubygems (LoadError) from /usr/share/phusion-passenger/helper-scripts/passenger-spawn-server:75
Rubygems have to be installed aswell or am i missing a package?
no such file to load — rubygems
Then “apt-get install rubygems”
In case anyone is using NGINX+IPV6:
It seems that something somewhere has changed and
listen 94.229.77.82:80; listen [2a01:348:226:dead:beef:dead:beef:dead]:80;
wont work anymore (you get “98: Address already in use”)
You have to change it to
listen 94.229.77.82:443; listen [2a01:348:226:dead:beef:dead:beef:dead]:443 ipv6only=on;
Hi.
[offtopic]
Is it possible to put this somewhere easier to get. I’ve browsed through few of tens minutes to get this.
It’s the differences between nginx light full extras etc…
https://docs.google.com/a/moolfreet.com/spreadsheet/ccc?key=0AjuNPnOoex7SdG5fUkhfc3BCSjJQbVVrQTg4UGU2YVE#gid=0